# Coding agents

Claude Code or Codex on your computer. @ one in a thread to give it work.

## Agent sessions

Each session you connect gets its own name, access and activity. Address it as @name from any thread to send it a request.

### Claude Code sessions

Connect the session you’re working in. Your conversation stays, and so does what it can do on your computer.

1. 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
   ```
3. Connect it in the session. It suggests a name from your project folder.

   ```bash
   /threadpage:connect
   ```
4. Your browser opens ThreadPage by itself. Check the session, change the name if you like, then choose **Connect**. On a computer without a browser, the session gives you a code to enter at thread.page/app/connect, then asks for the two digits the page shows.

A request starts there on its own, after any running turn. If it stays waiting, run `/threadpage:next` there.

With Pro, a session reads and adds notes in all your threads, and you can @ it; with a free account, it adds notes to your Inbox. That covers your notes in ThreadPage; on your computer it keeps the permissions it has. To narrow it, open it in Settings → Connections and choose **Manage access**.

To connect another session, run the last two steps in it. A session that reconnects within 18 hours comes back without the browser; after that, you approve its return once.

Don’t also add ThreadPage with `claude mcp add` in a session you connect this way: what it does through that is added via Claude Code, not under the session’s own name.

### Codex sessions

Connect the session you’re working in. Your conversation stays, and so does what it can do on your computer.

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

   ```bash
   codex plugin marketplace add ThreadPage/threadpage-companion && codex plugin add threadpage@threadpage
   ```
2. Quit Codex, then resume the same conversation.

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

   ```bash
   $threadpage:connect
   ```

A request starts there on its own, after any running turn.

## Client setup

This adds ThreadPage to every Claude Code or Codex session as tools it can use when you ask, with no name of its own to @. The server URL is `https://thread.page/mcp`.

### Codex

```bash
codex mcp add threadpage --url https://thread.page/mcp
```

The browser opens ThreadPage so you can choose access. You can choose a narrower level than the assistant asks for, such as Read only. See the [Codex authentication guide](https://learn.chatgpt.com/docs/extend/mcp?surface=cli).

If no browser opens, run `codex mcp login threadpage`. Run it once. To sign in again, remove the old connection first.

In a shared repository, keep instructions that link to your private threads in a personal instructions file you don’t commit.

### Claude Code

```bash
claude mcp add --transport http --scope user threadpage https://thread.page/mcp; claude mcp login threadpage
```

It adds ThreadPage for all your projects and signs you in: the browser opens ThreadPage so you can choose access. See the [Claude Code MCP guide](https://code.claude.com/docs/en/mcp). Run it once. To sign in again, remove the old connection first.

In Windows Command Prompt (cmd.exe), where `;` doesn’t separate commands, run this instead:

```bash
claude mcp add --transport http --scope user threadpage https://thread.page/mcp & claude mcp login threadpage
```

If `claude mcp login` is unknown, update Claude Code or use `/mcp` in a session.

If Claude Code is signed in with your claude.ai account, it now uses this connection instead of your Claude connection, so its notes say Added via Claude Code. In a shared repository, keep instructions that link to your private threads in a personal instructions file you don’t commit.

This connects Claude Code as an assistant: every session uses it, with no name of its own. To address one session with @ from your threads, connect it as a session instead ([Claude Code sessions](#claude-code-sessions)).

[See it in use: Claude Code writes, Codex reviews](https://thread.page/use-cases/claude-code-and-codex)