Ship agents that don't break. The open-source deterministic agent runtime — JarvisCore. Build whatever you want with it. Live office hours
Joined August 2026
- Tweets76
- Following21
- Followers22
- Likes103
Introducing multiplayer agents in JarvisCore 2.3!
Your team and its agents, in the same thread. Anyone asks in their own words, the work comes back as a proposal, and only the person who decides gets the Confirm button.
pip install -U jarviscore-framework
6/
Build your first multiplayer agent: jarviscore.developers.presco…
Code: github.com/Prescott-Data/jar…
5/
Bring it to where your team already talks. Slack works out of the box, or connect a room to your own product's chat.
Work runs on the JarvisCore mesh, so it carries on if a process stops.
4/
The agents work as the person who asked: their connected accounts, their access.
Work that used someone's private access is held for them first, and only reaches the room when they release it.
3/
Real teams talk over each other. When two people push back at the same moment, JarvisCore starts one revision, not two.
Anything added while work is running is kept and applied to its result. Nothing anyone asked for is lost, and only one version lands.
2/
A room is shared files plus the people allowed to touch them: owners, editors, viewers.
Every change the agents make is a proposal you can read as a diff, preview, accept or turn down. Nothing lands until a person confirms it.
Prescott Data Developers retweeted
Most multi-agent systems route every message through one orchestrator. When it goes down, everything stops.
Join @MutuaDevOps this Thursday for a live build-along: agents that find each other and talk directly, built on JarvisCore.
Oct 22 · 11:00 AM EAT · Discord discord.gg/DEgSVevF?event=15…
Most multi-agent systems route every message through one orchestrator. When it goes down, everything stops.
Join @MutuaDevOps this Thursday for a live build-along: agents that find each other and talk directly, built on JarvisCore.
Oct 22 · 11:00 AM EAT · Discord discord.gg/DEgSVevF?event=15…
Prescott Data Developers retweeted
anyway, I'm working on a major feature on the jarviscore cli aimed at making deployment of JarvisCore agents to servers/the cloud easier
Tomorrow on Developer Office Hours, @nyamberekimeu walks us through the new version of Odin: why we separated the graph engine from its database, and how.
Tue 13 Oct · 11:00 AM EAT (08:00 UTC)
Join us on Discord: discord.gg/geGbXhnR?event=15…
Today we have released JarvisCore v2.1.0 with fast RAG, stable atom life cycle, and better browser automation.
Please refer to jarviscore.developers.presco… for more details (v.2.0.0 and v2.1.0). Test it out and let us know what breaks 😊
or more reads:
1.jarviscore.developers.presco…
2.jarviscore.developers.presco…
3.jarviscore.developers.presco…
Prescott Data Developers retweeted
yes, you can read more here jarviscore.developers.presco…
JarvisCore v1.14.1 is out now!
What’s new: long running research agents.
Go try it out.
My hope for JarvisCore is that it shows a completely different way to build AI agents. Not as an experiment, but as an approach we've proven.
We open-sourced it a few months ago and kept building. Today it launches on Product Hunt. Here's what makes it different:
• No master agent. Agents are equal peers in a decentralised P2P mesh
• No MCP servers needed
• Zero-trust credentials
• Bounded memory (agents forget on a curve)
If you're building agents, I'd love to hear what's breaking for you.
JarvisCore has been shipping for a month. no master orchestrator, no MCP servers, no keys in .env.
This Friday it goes on product hunt. The full run too.
Prescott Data Developers retweeted
Picture a crop advisory agent that has talked to one farmer 400 times. At planting time it does not need all 400 conversations.
It needs only three, her soil is acidic, she limed in March, she prefers manure. The rest is history.
Join us as @devmarrie takes us through a technical deep dive of Athena memoryOS and the role it plays in agent's long term memory.
Tuesday 28th Sep 11am EAT : lnkd.in/dx6XFUiN
JarvisCore 1.13 now gives agents durable source workspaces.
Point a Mesh at a GitHub repo and the agent works from an immutable snapshot. Each step gets its own isolated copy-on-write workspace. Every edit is hash-guarded, so a stale edit is rejected instead of overwriting newer code. Commands and file changes come back as verified receipts, and only the accepted diff is kept.
You can also connect your own sources, like archives, datasets or document collections, through the same adapter interface.
pip install --upgrade jarviscore-framework
Learn more: jarviscore.developers.presco…
This is a detailed breakdown of what JarvisCore v1.12 shipped last week. Go test out how the Jev integration works for you and let us know about your experience in Discord discord.gg/SqzscmAfj
anyone with 1 hr to spare to sit through this recorded session i did yesterday on using Jev in an agent runtime (JarvisCore)?
Pass this test: can you ask Jev if you should watch the video?
youtube.com/watch?v=WH2vkIho…
