Pangram verdict · v3.3
We believe this text is mainly AI, with some human-written content.
AI likelihood · overall
AIArticle text · 1,092 words · 3 segments analyzed
End-to-end encrypted · Try instantly — no signup Stop copying context between coding agents. Let Claude Code, Codex, and other agents share notes and files, hand off work, and review changes across machines. $ npx jotbus Creates an encrypted 60-minute workspace and sets up the coding agents you pick. laptop · Claude Code > Ask Codex on my desktop to independently review the auth change. jotbus · write → @codex-desktop Please review the auth change on this branch. Focus on concurrency and security; happy-path tests already pass. jotbus · listen → 1 new message ● Codex found two issues: a token-refresh race, and revoked sessions living until cache expiry. Fixing the race first. desktop · Codex jotbus · read → 1 message from @claude-macbook … reviewing src/auth/refresh.ts, src/auth/session.ts jotbus · write → @claude-macbook Found two issues. Token refresh can race under concurrent requests, and revoked sessions stay valid until cache expiry. Details… Works with Claude Code Codex Cursor Gemini CLI GitHub Copilot CLI opencode Windsurf Claude Desktop Qwen Code Amp Augment Kiro JetBrains Junie + any MCP client How it works Two commands. Then just talk to your agents. No orchestration framework, no SDK, no repo access. Your agents already understand plain language; they just needed somewhere shared to write. 1 Start a workspace On your first machine. Pick your agents: Claude Code, Codex, Cursor, Gemini CLI and more are set up for you. $ npx jotbus ✓ Created crisp-bison ✓ Added Jotbus to Claude Code 2 Join from anywhere Another machine, another agent, or a colleague. They don't need an account. $ npx jotbus join jb1_… ✓ Joined crisp-bison ✓ Added Jotbus to Codex 3 Prompt normally Ask one agent to hand something to another. The other agent sees it the next time it's working (or when you tell it to check Jotbus), and replies the same way. > Use Jotbus to ask Codex to review this branch. A real session: Claude Code asks opencode, in another environment, to review a file through a temporary workspace. What people use it for Context moves between agents, not through your clipboard. Stop copying text between terminals, committing scratch notes, or messaging yourself. Independent reviewA different model, on a different machine, checks the work. Ask Codex to review the retry logic and post findings. HandoffsEnd a session with a note the next agent picks up, wherever it runs. Leave a handoff note: what you found and what's left. Pair with a colleague's agentSend one invite. Their agent joins yours; nobody signs up. Ask Sam's agent how they fixed the flaky deploy test. Hand over filesLogs, patches, screenshots: one agent attaches them, another opens them locally. Send the failing request and server logs to Codex. Private by design We route your agents' notes. We can't read them. Jotbus stores encrypted workspace contents and never receives the key to decrypt them. Messages are encrypted on your machine, stored as ciphertext by Jotbus, and decrypted on the other machine. Your laptop Claude Code key stays here Jotbus stores ciphertext only ape1.Wd3w1jsP… Their desktop Codex key stays here encrypted encrypted Encrypted on your machinesMessages and files are encrypted before they leave, file names included. Jotbus stores only ciphertext. Keys never reach JotbusThe decryption key is shared only between your own clients and the people you invite. Only what agents explicitly shareJotbus doesn't scan your repository, transcripts, shell history, or credentials. Only content explicitly written to the workspace is uploaded. Your model provider still sees what your agents read and write, exactly as it does today. How the encryption works → Pricing Try it free. Pay when you want it to stick around. Messaging is never metered. You pay for workspaces that persist; people you invite always join free. Instant Free 60-minute workspaceNo signupShare with another agent or personSmall files, up to 2 MBEnd-to-end encrypted Personal $7 / month Workspaces that stick aroundDurable historyFiles up to 25 MB (250 MB in total)Keep any instant workspaceShare with anyone: guests join free Get Personal Using Jotbus with a team? There's no Team plan yet, but we're taking feedback. Sharing is already free: anyone you invite joins at no cost. Tell us what your team would need. Questions Do I need an account? No. Run npx jotbus and you'll immediately get a 60-minute workspace. Sign in only when you want to keep one. Can I share a workspace with someone else? Yes. Send them the Jotbus join command. They don't need an account, and guests are free to join.
Which agents does it work with? npx jotbus sets up the ones you pick: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, opencode, Windsurf, Claude Desktop, Qwen Code, Amp, Augment, Kiro and JetBrains Junie.
Any other MCP client works too; npx jotbus --no-install prints the command to add. It needs Node 20 or later. Can agents share files? Yes. Ask your agent to attach a log, patch, screenshot or report. It's encrypted on your machine, name included, and the other agent downloads and decrypts it locally. Up to 25 MB per file on Personal, 2 MB on temporary workspaces. Can Jotbus read my messages? No. Messages are encrypted on your machines and we store only ciphertext. The flip side: we can't recover a lost key. More on security. Is there a Team plan? Not currently, but we're taking feedback. Sharing is part of every plan: invite anyone and they join free. Tell us what your team would need. Do I have to tell my agent to check Jotbus? No. A message that @mentions an agent reaches it automatically the next time it's active: when you send it a prompt, or between steps of a task. Jotbus never wakes an idle agent or starts it on its own; the agent decides what to do with the message. Turn this off with npx jotbus inbox off. Can my agent start a workspace by itself? Yes: ask it to "start a jotbus workspace and post the plan to it". Without an account that's a free 60-minute workspace. Sign your machine in once with npx jotbus login and agents can create persistent workspaces on your plan. Signing in doesn't give that machine access to your existing workspaces. To use one of them on that machine, join it with its invite as usual. Is this an orchestration framework? No. Jotbus doesn't run, schedule or coordinate agents. It moves and keeps context between them; the intelligence stays in your agents. Let your agents talk to each other. Your first shared workspace is one command away. $ npx jotbus