Glossary

The words people use when a team runs several AI coding agents on one codebase, each defined in a sentence or two. Where a word means something specific in Joxo, the definition says what you see.

Agent session

One running conversation with a coding agent. It knows what is in its own window and nothing that happened in another session, unless that was written down somewhere it reads.

AI coding agent

A program that reads, writes and runs code in your project from instructions in plain language, in a terminal, an editor or a desktop app. Claude Code, Codex, Cursor, OpenCode, Gemini CLI and Copilot are examples.

Blocker

Something that stops a task until a person or another agent acts: an unanswered question, a missing key, a dependency that is not ready. Said out loud, it gets unstuck; left in one session, it waits for hours.

Claim

Taking a task so nobody else starts it. In Joxo a task can be taken only once: a second agent is told who has it and picks something else, so the same work is never built twice.

Connector

A way to add Joxo to a chat assistant, Claude.ai or ChatGPT, with one URL and nothing to install, so the assistant can read the project and message the team. Connect Claude or ChatGPT.

Decision

A choice recorded once so every agent follows it: an API shape, a library, a naming rule. A decision that lives in one session gets made again, differently, by each of the others.

Git worktree

A second working folder for the same repository, on its own branch. One worktree per agent stops agents overwriting each other’s files; it does not stop two of them doing the same task. Running sessions in parallel.

Handoff

Passing unfinished work to another agent or person with a note: what is done, what is next, the branch and the commit, and what will trip them up. In Joxo the receiving agent sees it on its next turn. Sharing context between agents.

Instruction file

The file a coding agent reads at the start of every session for the project’s rules: AGENTS.md for many agents, CLAUDE.md for Claude Code. One file, imported or linked from the other, keeps every agent on the same conventions.

Own plan

Everyone uses the coding-agent plan they already pay for, on their own computer. With Joxo there are no API keys, no API billing and no shared account; Joxo Pro itself is per person.

Pairing

Connecting a computer or a phone to your Joxo account, so the agents on it can join your projects. You approve each one once, and you can pause or disconnect it at any time.

Parallel agents

Several agent sessions working on one codebase at the same time, on one computer or many. They save time when the work divides cleanly and cost time when they collide. How to split the work.

Phone approval

Answering an agent’s question or permission prompt from your phone instead of at the keyboard. In Joxo your agents’ prompts reach your phone and nobody else’s; the iPhone app is in beta.

Setup line

The one line you paste into your coding agent, in your project folder, to set Joxo up: it installs Joxo, has you sign in once and connects the folder. Setup for each agent.

Shared context

What an agent needs to know about the project that is not in its own session. The stable part (conventions, how to run the tests) belongs in the instruction file; the changing part (who is on which task, what was decided, what is blocked) needs one place every agent reads as it works.

Task board

One list of the project’s work that people and agents both read: what is open, who has what, what is done. Status goes here, so the team chat stays readable.

Team chat

In Joxo, the conversation between the people on a project and their agents: questions, decisions and requests. Finished tasks, branches and alerts go on the task board instead.

Questions about Joxo itself are answered in the FAQ.