ThreadPage plugins for Claude Code and Codex

ThreadPage keeps each project in one thread of notes. These plugins connect your Claude Code and Codex sessions to it, each under its own @name. On ThreadPage Pro with Sync on, a session reads your threads and adds notes, and you ask it from any thread by its @name; on Free, it adds notes to your Inbox (Free and Pro). Step by step: thread.page/help/connections/coding-agents.

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 <name> 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 <name>); 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, set Who can ask it to No one, or Pause 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.

Free and Pro

On ThreadPage Pro with Sync on, a connected session reads your threads and adds notes, and you ask it by its @name. On Free, or on Pro without Sync, it only adds notes to your Inbox: it doesn't read your notes and no one can ask it. A name whose access you never changed follows your plan: once you're on Pro with Sync on, it reads, adds and can be asked too. Only you can send a request, unless you let your agents ask each other. Anything else waits for your permission. You can try Pro free for 14 days, once per email address, without a card: thread.page/pricing.

Handoff

A free skill for Claude Code, Codex and any agent that reads skills: it writes where a session stopped (done, left, blocked) into .handoff/ in your project, and reads the last handoff back in the next session. It needs no account and runs no hooks or server. With ThreadPage's tools in the session, a copy goes to your Inbox, or on Pro with Sync on to a thread the next session reads.

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

codex plugin marketplace add ThreadPage/threadpage-companion
codex plugin add handoff@threadpage

npx skills add ThreadPage/threadpage-companion --skill handoff

How to use it and how to keep it in a repository: plugins/handoff/README.md. With the plugins above on Pro with Sync on, connecting a session in that folder also shows it the last handoff of the thread in .handoff/thread, and asks it to add a note there.

The MCP server

Claude, ChatGPT, Claude Code and Codex can also connect to your notes through the ThreadPage MCP server at https://thread.page/mcp, with OAuth sign-in in your browser: thread.page/help/connections/mcp. In a Claude Code session you connect with the plugin, don't also add the server with claude mcp add: what the session does through it is then added via Claude Code, not under the session's own name.

More

What each plugin runs, sends and keeps: plugins/threadpage/README.md, plugins/threadpage-codex/README.md, plugins/handoff/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.

• ThreadPage: thread.page
• What each connection can do, and how to undo what it did: thread.page/help/connections
• Privacy: thread.page/privacy