Problem solved

Teams using AI coding agents often work in isolated sessions, so decisions, context, and handoffs are lost between different plans and machines. Joxo solves this by providing a shared project with one memory, task board, and handoff channel, allowing agents from different teammates to continue work without re-explaining context or manually copying information.

Use cases

• Run a hackathon team where three developers use different AI coding agent plans on one shared project.
• Propagate architectural decisions like database choice from one teammate's agent to all other agents.
• Assign and claim coding tasks on a shared board so agents continue from the next commit or branch.
• Hand off a payments flow or auth screen between Claude Code, Codex, Cursor, or Gemini CLI sessions.
• Send a command from a phone to wake a development machine and run a job.
• Keep a complete day-of-demo history of decisions, blockers, and handoffs across all teammates' agents.
• Coordinate agent sessions for prototypes and early startup MVPs without an enterprise account.

Audience

• Developers
• Startups
• Hobbyists

Pros

• Lets each teammate keep their existing AI coding agent subscription with no API keys or shared enterprise plan required.
• One-prompt setup lets an agent install the connector and pair the project.
• Shared memory, task board, and handoffs keep multiple agents working on the same project context.
• Supports 28 coding agents including Claude Code, Codex, Cursor, Gemini CLI, and OpenCode.
• Peer messages are fenced as untrusted context, and live file access is off by default.

Cons

• Early access; the phone app is not yet in app stores and push notifications may be limited.
• Hosting a project requires an Apple Silicon Mac that stays online.
• Setup depends on Node.js 22.13+ and compatible agent installations on each computer.
• There is no chat box; the tool only passes messages between existing agent sessions.
• The relay is hosted, so team coordination depends on Joxo's service availability.