Looks pretty cool, although I'm not sure I see the advantage over a skill using something like a private git repo / file store / server?
So far, I've used that, a UNIX-socket inspired approach to push/pull with a remote git (hosted on my server) that the branches/files can be tossed to, and pulled via other agent. Skill instructs them to make a copy-paste ready instruction for the other prompt.
Sounds like your setup achieves basically the same thing as Jotbus. If you've already got repo/server/skills wired up for this, Jotbus probably wouldn't buy you much.
I had basically 2 motivations for building it:
- I was frequently spinning up places to dump stuff for people/agents. I wanted to make it simple across environments, and have no infra or glue to manage.
- a lot of what I pass around is mid-work/transient - logs, partial implementations, screenshots, etc. Not ready for a commit, don't necessarily want it in git history. Wanted to make it easy to hand off and keep going.
So it's not exactly a novel primitive, it's just a tool to make it quicker/easier.
I frequently have to copy-paste context and files between different coding agents, either between my different environments/machines, or from me to teammates.
I built Jotbus so I wouldn’t have to keep doing that.
You can try it free with:
npx jotbus
No login or signup required. It creates a temporary shared workspace and connects it to the coding agents you use via MCP.
Once it's installed, you can just tell your agent something like
"write this handoff note to jotbus"
or
"send that PDF over Jotbus to @codex"
Then another agent can join the workspace and pull the context.
Messages and files are end-to-end encrypted. Encryption happens locally, and the hosted service only stores ciphertext; the workspace key never reaches Jotbus.
I built something similar recently but it also supports file sharing. So you can read a markdown file in the UI, read code in UI, share with a friend, share with an agent, etc. https://agentdrop.lol/
So far, I've used that, a UNIX-socket inspired approach to push/pull with a remote git (hosted on my server) that the branches/files can be tossed to, and pulled via other agent. Skill instructs them to make a copy-paste ready instruction for the other prompt.
Why'd Jotbus be worth the overhead?
Sounds like your setup achieves basically the same thing as Jotbus. If you've already got repo/server/skills wired up for this, Jotbus probably wouldn't buy you much.
I had basically 2 motivations for building it:
- I was frequently spinning up places to dump stuff for people/agents. I wanted to make it simple across environments, and have no infra or glue to manage.
- a lot of what I pass around is mid-work/transient - logs, partial implementations, screenshots, etc. Not ready for a commit, don't necessarily want it in git history. Wanted to make it easy to hand off and keep going.
So it's not exactly a novel primitive, it's just a tool to make it quicker/easier.
I frequently have to copy-paste context and files between different coding agents, either between my different environments/machines, or from me to teammates.
I built Jotbus so I wouldn’t have to keep doing that.
You can try it free with:
npx jotbus
No login or signup required. It creates a temporary shared workspace and connects it to the coding agents you use via MCP.
Once it's installed, you can just tell your agent something like
"write this handoff note to jotbus"
or
"send that PDF over Jotbus to @codex"
Then another agent can join the workspace and pull the context.
Messages and files are end-to-end encrypted. Encryption happens locally, and the hosted service only stores ciphertext; the workspace key never reaches Jotbus.
If you try it out, I'd love feedback!
Thanks!