ThreadPage

ThreadPage local clients

The ThreadPage plugins for Claude Code and Codex: each session you connect gets its own name in ThreadPage. On ThreadPage Pro with Sync on, the session reads your threads, adds notes, and takes the requests you address to its @name. On Free, or on Pro without Sync, it only adds notes to your Inbox: it doesn't read your notes and takes no requests. A name whose access you never changed follows your plan: once you're on Pro with Sync on, it reads, adds and takes requests too. Only you, the account's owner, can address a request to your sessions.

This repository is a read-only mirror. It is updated only from tagged ThreadPage releases, and changes are made only by ThreadPage. To report a security problem, see SECURITY.md.

The plugins run on macOS, Linux and Windows through WSL, and need Node.js 22.20 or later on Node 22, or 24.8 or later. Native Windows isn't supported: the Claude Code plugin's hooks need sh, and there neither plugin keeps this computer's ThreadPage key between sessions.

Claude Code

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

Then, in a Claude Code session, /threadpage:connect connects it under a name suggested from its folder (/threadpage:connect as picks one); you approve it once in ThreadPage in your browser. A request addressed to the session reaches it through its inbox and doesn't wait for anyone at the terminal: an idle session starts a turn by itself, a busy one reads it between tool calls. It runs with that session's own mode, rules and approvals, so a session that skips approval prompts carries it out without asking. To keep requests from starting by themselves, set "Messages from your other sessions" (crossSessionInbound) in /config to hold or refuse; /threadpage:next then takes them.

Codex

codex plugin marketplace add ThreadPage/threadpage-companion

codex plugin add threadpage@threadpage

Then start a new Codex session, send it any message, and type $threadpage:connect (or $threadpage:connect as ); you approve each connection in ThreadPage in your browser. A request addressed to the session starts once it has no running turn, with the session's own sandbox and approval settings, so under --ask-for-approval never it runs without asking; $threadpage:next takes the oldest waiting request. Live in ThreadPage means the Codex session is loaded, not that anyone is looking at it. To stop requests from starting in a session, Disconnect it in ThreadPage. To give a Codex session only its own name, start it with codex --disable apps, so the ChatGPT apps connector does not add a second ThreadPage connection.

More

What each plugin runs, sends and keeps: plugins/threadpage/README.md, plugins/threadpage-codex/README.md and SECURITY.md. RELEASES.json lists each release and the version of each client in it; CHANGELOG.md has each release's notes and, from the second release on, a link to its changes.