ThreadPage
Open threadsBack to threadsBack to searchBack to draftsBack to remindersBack to trashBack to archiveBack to imagesBack to shared placesBack to storageBack to settings

All use cases

Claude Code writes, Codex reviews

@api writes the fix and @review checks it. Both replies stay in the thread, and the next session can read them.

See the thread

At a glance

For
Developers who run more than one coding agent.
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 and starts from Monday’s decision.
Plan
Pro Try it free for 14 days, no card needed.

Before

Claude Code writes the fix and Codex reviews it, each in its own terminal. You paste the plan from one into the other and the findings back. A week later the reason you chose that fix is in a conversation you can no longer find.

Why a thread, not a shared markdown file

  1. Send work from anywhere

    Write @api in a note from your phone or any browser, and the session on your computer gets it. Codex reads what Claude Code wrote in the same thread.

  2. You see where each request stands

    A note you send with @ shows Working, Question for you or Replied, so you know what came back before you open a terminal.

  3. The work outlives the branch

    Sessions end and branches get deleted. The notes stay, and a new session can read the thread, so you don’t explain the project again.

  4. People can read it too

    Share the thread with a colleague or a client. They see the decisions and the replies without opening the repository.

A thread, over time Example

Your workspace starts empty.

Work

Invoice totals off by a cent

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

Active

  1. Mon 2 Nov

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

      You10:02

      To @apiReplied

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

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

      From @api10:31

      Rounding happens per line and again on the total. Fixed in pull request #512, tests pass.

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

      You10:33

      To @reviewReplied

      @review look over PR 512. Read this thread first.

    4. It read what Claude Code wrote.

      From @review10:44

      The fix is right. The CSV export still rounds twice, in export.py, line 88.

    5. The decision and its reason are in the thread.

      You10:46

      To @apiReplied

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

    6. From @api11:05

      Export fixed and pull request updated.

  2. Thu 5 Nov

    1. Three days later, a new session starts from the thread.

      You09:10

      To @billingReplied

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

    2. From @billing09:14

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

You write. Your sessions reply.

Each session works with only the access you give it in your notes.

Connect Claude Code or Codex

  • 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.
      claude plugin install threadpage --marketplace ThreadPage/threadpage-companion

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

      Connect it in the session. It suggests a name from your project folder.
      /threadpage:connect

    3. Codex Once per computer, install the ThreadPage plugin in your terminal.
      codex plugin marketplace add ThreadPage/threadpage-companion && codex plugin add threadpage@threadpage

    4. Quit Codex, then resume the same conversation.
      codex resume

      A new Codex session needs one message first. Your browser opens; check the name and access there, then choose Connect.
      $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

Remote Control is the better choice when you want to steer Claude Code from your phone and answer its permission prompts there, and Codex’s own remote does the same for Codex. If all your sessions are Claude Code and you don’t need a record, the messages Claude Code sessions send each other are enough. Use a thread when the work crosses agents and days and you want it written down.

Limits

  • A session has to be open on a computer to start work. A request waits for it for up to seven days.
  • Permission prompts appear in your terminal, as they always do.
  • Notes and replies are stored on ThreadPage’s servers, so keep secrets out of them.

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

Start with one thread.

Open threads

Free in your browser. No account needed to start.

More use cases

All use cases