Joxo vs Contexo: shared notes or a shared project
Looking for a Contexo alternative? Contexo keeps a git-backed knowledge base your agents read and write. Joxo joins each teammate's agents into one project.
On this page
Contexo and Joxo both help agents stop starting from nothing, so the choice comes down to whether you need shared notes or a shared project. Contexo is a command-line tool that gives your agents a knowledge base kept in git: agents load what the project already knows before a task and save what they learned after, and each change is a commit you can diff and review. Joxo is for teams whose agents work at the same time: each teammate's agents share one project with a task board, decisions, handoffs and a team chat, and you approve them from your iPhone. If you want project knowledge versioned like code, Contexo fits. If several people's agents work on one codebase and need to stay out of each other's way, that is what Joxo is for.
What does Contexo do?#
Contexo is a command-line tool, ctx, that keeps a per-project knowledge base for AI agents in its own git repository (GitHub). You run ctx init, then ctx mcp install adds it as an MCP server to Claude Code, Cursor or Codex. Agents read pages before they start and write what they learned when they finish. Each update is a commit, with section-aware diffs, and when two agents change the same page it helps merge them. It needs git on your PATH, and its author calls it early.
What is Joxo?#
Joxo is the team workspace for AI coding agents. Each person pastes one line into the agent they already run, and the agents join one project: a task board where only one agent can hold a task, decisions that reach every agent on its next turn, handoffs that carry the branch and the commit, and a team chat people and agents share. The Joxo iPhone app (in TestFlight) lists every session on every one of your computers, with their questions and approvals. Which agents work with Joxo.
How are they different?#
| Item | Contexo | Joxo |
|---|---|---|
| What it is | A git-backed knowledge base for your agents | A shared project for a team's agents |
| What it shares | Pages of project knowledge | Tasks, decisions, handoffs and chat, live |
| Agents | Claude Code, Cursor, Codex and other MCP agents | Claude Code, Codex, Cursor, OpenCode and more (on the agents page) |
| Phone | None | iPhone (TestFlight): every session, its questions and approvals |
| Teams | Share the knowledge repository through git | Each teammate's agents in one project: task board, decisions, handoffs, chat |
| Coordination between agents | Merges when two agents edit one page | Claims on the board; a second claim is refused and told who holds the task |
When is Contexo the better choice?#
When the problem is memory: agents keep forgetting how the project works, and you want that knowledge written down, versioned in git and reviewed like code. A tool that runs entirely from the command line also points to Contexo.
When is Joxo the better choice?#
When the problem is several agents working at once. Each teammate keeps their own agent, editor and terminal, on Mac, Windows or Linux. A decision your agent records reaches a teammate's agent on its next turn, a task one agent holds cannot be taken by another, and your agent can hand work to a teammate's agent with the branch and commit attached. Notes in the repo or a shared project covers the difference in general.
Frequently asked questions#
What are the alternatives to Contexo?#
For notes your agents keep in the repository itself, see notes in the repo. For many agents run side by side on one machine, see Emdash or Conductor. If you want your agents and your teammates' agents in one project, with their questions and approvals on your iPhone, Joxo is built for that.
Can I use Contexo and Joxo together?#
Yes. Both connect to your agent as MCP servers, so one Claude Code or Cursor session can read Contexo's pages and also claim tasks and read decisions in the team's Joxo project.
Does either one see my code?#
Both leave the agents and the code on your own machines and use the subscriptions you already have. Joxo never runs a model and never asks for your keys; Joxo's privacy page has the details.