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

Which session is waiting on you

Claude Code in three repositories, Codex in two. For you shows the one with a question, the one waiting for your approval and the replies you haven’t read.

See the thread

At a glance

For
Developers with several Claude Code and Codex sessions open at once.
You keep
A thread per job, and a name for each session: @web, @payments, @review.
Comes in
  • Questions, replies and requests that wait for your approval, listed on For you.
  • Each reply, as a note in its job’s thread.
The moment
At 15:20 For you lists two sessions that need you and one reply you haven’t read. The sessions still working stay off the list.
Plan
Pro From USD 7.99 a month. 14 days free, no card.

Before

Claude Code runs in three terminals and Codex in two. One of them asked you something forty minutes ago, another has sat at a permission prompt since lunch, and you find out by clicking through every tab. The one that finished first has been idle for an hour.

Why a thread, not a row of terminal tabs

  1. One list of what needs you

    For you puts questions and requests waiting for your approval first, then the replies you haven’t read. A session that’s busy working stays off it.

  2. Each request shows its state

    The line under your note says Queued in the session, Working, Question for you or Replied in 6 min, so you know which tab to open before you open one.

  3. Answer from where you read

    Choose Answer on the request’s line, and your note goes to that session. An approval still happens in the terminal, and the note names the computer.

  4. The replies outlive the tabs

    Close a terminal, and its replies stay in the thread, where the next session reads them.

The moment

Thursday, 15:20, back from a call: what needs you across five sessions.

For you

  • Payments

    Refund rounding

    To @paymentsQuestion for you

    @payments make refunds round the way invoices do now.

  • Web

    Vite 8 upgrade

    To @webWaiting for your approval on MacBook Pro

    @web upgrade to Vite 8 on a branch, fix what breaks, then run the build and the unit tests.

  • API

    Rate limits

    To @reviewReplied in 6 min

    @review check the limiter against the spec note.

A thread, over time Example

Your workspace starts empty.

Web

Vite 8 upgrade

Active

  1. Thu 22 Oct

    1. At 14:02 you send the upgrade and go back to the payments repository.

      You14:02

      To @webReplied in 1 hr

      @web upgrade to Vite 8 on a branch, fix what breaks, then run the build and the unit tests.

    2. At 15:20 For you said @web was waiting for your approval on MacBook Pro.

      You15:24

      It was stuck on a permission prompt from before lunch. Approved it in the terminal, and it moved on to this.

    3. The reply says what it changed and why.

      From @web15:51

      Done on the vite-8 branch. The build takes 29 s instead of 41 s, and the unit tests pass.

      ChangeWhy
      Legacy plugin removedVite 8 doesn’t need it
      Test runner updatedThe old version won’t start

    4. Codex reviews it from the same thread.

      You15:55

      To @reviewWorking

      @review look over the vite-8 branch. Read this thread first.

You write. Your sessions reply.

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

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.

  • Know when one needs you

    A notification comes when a session asks, replies or needs you, on every browser where you turned them on.

    Set it up

    NotificationsQuiet hours

    1. In Settings → Notifications, turn on Notifications in this browser on the phone or computer where you want them.
    2. Turn on Quiet hours for the hours you sleep. What comes in then arrives silently when they end, one per thread.
    3. On iPhone, add ThreadPage to the Home Screen first: in Safari, tap Share, then Add to Home Screen. Open it from there, sign in and turn notifications on.

Also

Remote Control shows a Claude Code session’s questions and permission prompts on your phone. Use a thread when Codex sessions are in the mix too, or when you want the replies kept after the tabs are closed.

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.

Claude Code, Codex, Vite, 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

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

Start a thread

More use cases

All use cases