Try it: a two-tool handoff in 10 minutes

This guide walks you through one handoff from start to finish. You start a small task in Claude Code, stop it partway, hand it to Codex in Seggo, and watch Codex carry on from where Claude Code stopped.

It uses a tiny made-up project called example-app, so nothing you care about is touched.

Before you start

• Seggo is installed and open. See Install Seggo and First run.
• Claude Code and Codex are both installed, and you can start them from a terminal (claude and codex).
• Git is installed. Seggo gives the task its own folder and branch, and that needs a git project.

You can swap the tools around. Any two tools you can turn on work the same way.

1. Make a tiny sample project

In a terminal, make a new folder with a short to-do list and save it as a first commit:

mkdir example-app && cd example-app
git init
cat > TODO.md <<'EOF'
# Tip calculator

1. Make index.html with a bill amount box, a tip % box and a Calculate button.
2. Add script.js that shows the tip and the total when you click Calculate.
3. Add a README.md that says how to open the page.
EOF
git add TODO.md
git commit -m "Add TODO"

What you should see: a folder called example-app with one file, TODO.md, and one commit.

2. Turn on both tools for this project

In Seggo, open Tools in the sidebar.

1. Switch Claude Code On. When it asks which projects, add the example-app folder by its path. Read the preview and click Confirm.
2. Do the same for Codex.

What you should see: both switches show On in 1 project. Each change is listed under What Seggo changed, with Undo.

3. Add the task

Pick example-app in the sidebar, open its Tasks tab, and click New task. Call it Build the tip calculator from TODO.md.

What you should see: the task card in To do, marked Not started.

4. Start the task in Claude Code

In the terminal, inside example-app, start Claude Code:

claude

Then ask:

Take the next task from Seggo. Do only step 1 of TODO.md, commit it, save a Seggo checkpoint, then stop and wait for me.

What you should see: Claude Code says which folder and branch it will work in (a folder beside example-app, on a branch starting with seggo/). In Seggo, the card moves to In progress, shows Claude Code, and has a status chip such as Active. The Working now strip at the top of the project says Claude Code is on this task.

5. Stop Claude Code partway

Once Claude Code has finished step 1 and saved its checkpoint, quit it with /exit. This is the same as Claude Code running out of usage halfway through a task.

What you should see: in Seggo, click the task card to open its panel. Under Progress, the newest checkpoint says step 1 is done, steps 2 and 3 remain, and what to do next. The Is it moving? section shows the task’s status, when it last did something, and a plain reason. After a while with no activity, the chip changes from Active to Quiet. You don’t need to wait for that.

6. Hand the task to Codex

In the task’s panel (or the card’s ⋯ menu), choose Hand to… and pick Codex. Read the prompt Seggo shows, then copy it.

Start Codex in a terminal and paste the prompt as your first message:

codex

If you’ve turned on Let Seggo start tools for me, you can click Open in Codex instead. Seggo shows exactly what it will run before it does anything.

What you should see: Codex reads the task and the latest checkpoint first. It works in the same task folder and branch Claude Code used. It does not redo step 1. It picks up at step 2.

7. Watch Codex finish

Let Codex do steps 2 and 3. When it’s done, it marks the task finished.

What you should see: the card moves to Needs review. Its Progress shows Claude Code’s checkpoint, then Codex’s, one after the other. In the task folder, index.html, script.js and README.md all exist. Open index.html in your browser and try a tip.

That’s the handoff. The work moved from one tool to the other with what was done, what failed and what’s next intact.

Optional: ask the other tool to review

1. On the Tasks tab, open the ⋯ menu and choose Project settings…. Under Peer review, check Suggest a reviewer when done.
2. Open the task in Needs review and click Ask Claude Code to review (also in the card’s menu as Ask a teammate to review…). Read the prompt. Nothing opens until you click Open, or you can copy it into Claude Code yourself.

What you should see: Claude Code reviews Codex’s work and either approves it or asks for changes. If it asks for changes, its notes go back to Codex. Seggo never suggests the tool that did the work as its own reviewer, and the final OK is always yours.

Optional: see what’s moving and what works

• Is a task moving? Every task in progress has a chip on its card, such as Active, Quiet or Stopped at limit. Open the task for the reason. If it’s stuck, the panel offers Hand to… and Send back to To do.
• What works with each tool. Open Tools. The grid at the top has one row per tool and a chip for each thing Seggo can do with it: Works, Needs a fix, Not available or Not installed. A Fix button next to a Needs a fix chip shows how to fix it.

What you should see: Claude Code and Codex both show Works for Connected to Seggo.

Tidy up

When you’re done, open Ready to merge to merge the task or remove its folder. Then switch both tools Off in Tools (or use Undo in What Seggo changed), and delete the example-app folder.

If something doesn’t work

• A tool says Seggo is unavailable, or ignores the task. Open Tools and check the What works with each tool grid. Click Fix next to any Needs a fix chip, then start a new session in that tool. See Connect your tools.
• The tool didn’t save a checkpoint before you quit. Start it again and ask: “Save a Seggo checkpoint for this task.” Then quit and hand off.
• The tool made its own folder or branch. Tell it to use the folder and branch Seggo gave it, then carry on.
• Hand to… doesn’t list Codex. Seggo only lists tools it found on this computer. Check Codex’s row in the grid on Tools.
• Something else. Click Send feedback at the bottom of Seggo’s sidebar. It has no history in it. See Troubleshooting and feedback.