# Claude Code writes, Codex reviews

@api writes the fix and @review checks it. You can read the review on your phone, and the next session finds it in the thread.

## At a glance

- **For:** Developers who run Claude Code and Codex on the same repository.
- **You keep:** One thread per job, and a name for each session.
- **Comes in:**
  - Replies from your sessions, as notes.
  - Whatever you add yourself: screenshots, logs, decisions.
- **The moment:** On Thursday a new session reads the thread, review included, and starts from Monday’s decision.
- **Plan:** Pro · From USD 7.99 a month. 14 days free, no card.

## Before

Claude Code writes the fix, Codex reviews it, and the review stays in the terminal where you asked for it. Your phone can’t reach it, and the session that picks up the work on Thursday starts without it. When a colleague asks why the export still rounds twice, you scroll back to find out.

## Why a thread, not a review inside the session

### The next session reads the review

Codex’s findings sit in a note under Claude Code’s fix. On Thursday a new session reads both, along with the decision you wrote under them.

### You read it from your phone

Your note to @review shows Working, then Replied in 11 min. Open the thread in any browser, and the review is there.

### A colleague reads it too

Share the thread, and they see the fix, the review and your reason without opening the repository.

### Each session keeps its own setup

Write to @api, and the session on your computer works with its own conversation, repository and permissions. Codex reads what Claude Code wrote in the same thread.

## A thread, over time

Your workspace starts empty.

### Invoice totals off by a cent

Totals on multi-currency invoices are off by a cent.

Work · Active · Shared · Sam

#### Mon 19 Oct

*You write to one session by name, from any browser.*

**You** · 10:02

To **@api** Replied in 29 min

@api invoice totals are off by a cent on multi-currency invoices. Find out why and fix it on a branch.

*Its reply is a note you can search and share.*

**From @api** · 10:31

We round each line, then round the total again. Fixed in pull request #512; the tests pass.

*Codex gets the same thread, with nothing pasted.*

**You** · 10:33

To **@review** Replied in 11 min

@review look over pull request #512. Read this thread first.

*You read the review on your phone, between two meetings.*

**From @review** · 10:44

The fix is correct. The CSV export still rounds twice, though: export.py, line 88.

*Your decision, with the reason behind it.*

**You** · 10:46

To **@api** Replied in 19 min

@api fix the export too. We round once, on the total, because finance reconciles against totals.

**From @api** · 11:05

Export fixed, pull request updated.

*Sam gets the thread, review included.*

**You** · 11:10

Shared this thread with Sam at Can add notes, so he can approve #512.

*His approval, in the same thread.*

**Sam** · 13:20

Read the review and the rounding rule. Approving #512.

#### Thu 22 Oct

*Thursday: a new session starts from the thread. The thread is shared now, so you choose Allow here once.*

**You** · 09:10

To **@billing** Replied in 4 min

@billing refunds are next. Read this thread and follow the rounding rule.

**From @billing** · 09:14

Refunds round per line today. I’ll move them to Monday’s rule.

## You write. Your sessions reply.

Each session reaches only the notes you give it access to.

[Connect Claude Code or Codex](https://thread.page/help/connections/coding-agents.md#sessions)

### Connect your sessions

Install the plugin once per computer. Then connect every session you run, each under its own name.

#### Set it up

Coding agent

1. **Claude Code** Once per computer, install the ThreadPage plugin in your terminal.

   ```bash
   claude plugin install threadpage --marketplace ThreadPage/threadpage-companion
   ```

2. Quit Claude Code, then reopen your conversation with ThreadPage.

   ```bash
   claude --continue
   ```

   Connect it in the session. It suggests a name from your project folder.

   ```bash
   /threadpage:connect
   ```

3. **Codex** Once per computer, install the ThreadPage plugin in your terminal.

   ```bash
   codex plugin marketplace add ThreadPage/threadpage-companion && codex plugin add threadpage@threadpage
   ```

4. Quit Codex, then resume the same conversation.

   ```bash
   codex resume
   ```

   A new Codex session needs one message first. Your browser opens; check the name and access there, then choose Connect.

   ```bash
   $threadpage:connect
   ```

5. Your browser opens ThreadPage. The name comes from the project folder; change it if you like, then choose **Connect**. To connect another session, run the connect command in it.

## Also

OpenAI’s codex-plugin-cc runs a Codex review inside Claude Code with `/codex:review`. That’s the simpler route when the review only has to reach the session that asked for it. Remote Control lets you steer Claude Code and answer its permission prompts from your phone. Use a thread when the review has to be read after the session ends, by the next session or by someone else.

## Limits

- A session has to be open on a computer that stays awake. A request waits up to seven days for it.
- Permission prompts appear in your terminal, as they always do. If one holds up your request, the note says Waiting for your approval and names the computer.
- Notes and replies are stored on ThreadPage’s servers and aren’t end-to-end encrypted, so keep secrets out of them.
- In a thread you share, a session answers only after you choose Allow here once.

Claude Code, Codex, codex-plugin-cc, and Remote Control are the names of their owners. ThreadPage is independent and not affiliated with or endorsed by them.

## Start with one thread.

[Start free trial](https://thread.page/auth/sign-up?returnTo=%2Fapp%2Fsettings%2Fconnections%2Fcoding-agents%23trial)

14 days of Pro, no card. Then from USD 7.99 a month.

[Start a thread](https://thread.page/app)

More use cases

### [Planned in Claude, built by Claude Code](https://thread.page/use-cases/spec-to-code.md)

Work the feature out with Claude or ChatGPT, then have it save the spec as a note. @shop builds from that note and @review checks the branch against it.

Pro · an app and two sessions

### [Where your coding agent stopped](https://thread.page/use-cases/agent-work-log.md)

Claude Code hits its limit on Monday afternoon. You write to @codex, and it carries on from the pinned plan and the last note.

Pro · Claude Code and Codex

[A notes app with MCP for Claude, ChatGPT and Codex](https://thread.page/notes-mcp.md)

[All use cases](https://thread.page/use-cases.md)
