Coming from Claude Code or Codex
If you already work with Claude Code or Codex in a terminal, rev0 runs the same CLI for you, one session per ticket, and adds a board around it. This page maps what you know onto the board, and shows how to go back to the terminal when you want to.
Before you begin
Section titled “Before you begin”rev0 drives the CLI you already have. Sign it in once from the board, in Settings > Agents, or keep the login you made in a terminal: both are the same login.
What maps to what
Section titled “What maps to what”| In the terminal | On the board |
|---|---|
| A session: you type a prompt and watch | A ticket. The description is the prompt; the agent runs in its own branch and worktree, and its timeline streams live on the ticket. |
| Several terminals on one repo | Several tickets. Each gets its own worktree, so up to Max concurrent agents (8 after setup) run at once without touching each other’s files. |
| Plan mode (Shift+Tab) | A plan mode ticket: Plan, Flow plan or Interactive plan. The agent cannot edit until you click Accept plan, and you can annotate the plan line by line first. |
| Typing while it works | Replying on the ticket. Your reply reaches the running agent; a side question (/btw) gets an answer without interrupting it. |
| A permission prompt | A tool request: the ticket parks in Pending Action with an approve or decline panel, and you can answer from your phone. |
| A slash command | A Command ticket (Command (runs a /skill)), or the report library on the Create form. |
/loop, or a cron job running claude -p | A Loop ticket (Loop (runs on a cron schedule)): a schedule and a pipeline you edit and approve. Goal runs until an objective is met. |
| Subagents | Subtickets. An orchestrating agent can split broad work into a pipeline of child tickets. |
git diff, then a merge by hand | In Review: the branch’s diff, its commits and checks, then Merge. |
--resume to continue | Automatic. A ticket that parks (a question, a plan, a limit) resumes the same session when you answer. |
What keeps working
Section titled “What keeps working”- CLAUDE.md. A Claude run loads the repository’s
CLAUDE.mdand your user settings in~/.claude, as the CLI does in a terminal. - Skills. Your own skills in
~/.claude/skillsare available to Claude runs, and skills the board installs go to every engine that reads skills. - MCP servers. A Claude run gets the MCP servers the board lists in
Settings > Connections > MCP servers, plus the servers in your
~/.claude.jsonand your claude.ai connectors. Tick Board list only. there to give every run only the board’s list. A Codex run reads~/.codex/config.tomlinstead of your Claude servers. See Connect an MCP client. - Your models. Pick any model in a ticket’s Model field, including a custom id; the engine follows the model.
What the board adds
Section titled “What the board adds”- A queue: tickets wait in To Do and start as agents free up, even while you are away.
- Isolation: every ticket works on its own branch, and nothing reaches your base branch until you merge it.
- A place to answer: Pending Action collects every plan, question and tool request, from any device.
- Checks before review: tests agreed in the plan, and the code quality gate the Developer profile turns on, run before a ticket reaches In Review.
- Memory across runs: agents propose Knowledge Base pages with what they learned, so the next run does not rediscover it.
- A record: every ticket keeps its transcript, diff, commits, artifacts and cost.
Take a ticket back to your terminal
Section titled “Take a ticket back to your terminal”- Open the ticket.
- In the ticket’s … menu, hover Open in… and pick Claude Code (or Codex, Cursor, Gemini CLI).
Result: a terminal opens in the ticket’s worktree and runs claude --resume on the agent’s
session, so you continue exactly where the agent stopped. Only the engine that ran the ticket
resumes its session (the menu marks it resumes session); any other pick, or a ticket with no
session yet, opens a fresh CLI there instead. On a machine where no terminal can
open, a dialog shows the command with Copy command to run it yourself.
Commit what you change in the worktree on the ticket’s branch, and it shows up in the ticket’s diff and merges with the rest.
Drive the board from Claude Code
Section titled “Drive the board from Claude Code”The board is also an MCP server: add it to Claude Code and you can create tickets, read their status and answer them from a terminal session. See Use the board from Claude Code.
Related
Section titled “Related”- Your first finished ticket, to try the whole loop once.
- Write a ticket an agent can finish, since a ticket is a prompt nobody follows up on.
- Run Codex or Cursor instead of Claude Code, to switch engines.
- Which tool when, to choose between a ticket, a Loop and a Goal.