# Ask before bed, read the reply at breakfast

Write to @shop before you log off. If it has a question in the night, you see it at breakfast. The reply comes with screenshots.

## At a glance

- **For:** Developers who leave long jobs running overnight.
- **You keep:** A thread per job, and a session named after its project, such as @shop.
- **Comes in:**
  - The session’s question, if it has one, held until your quiet hours end.
  - Its reply, as a note with tables and screenshots.
- **The moment:** At 07:12, For you on your phone shows one question. You answer in a line, and by 08:00 the reply is in the thread.
- **Plan:** Pro · From USD 7.99 a month. 14 days free, no card.

## Before

At 23:00 you give Claude Code a long job and go to bed. At 23:31 it stops to ask whether it may rewrite two tests, then waits all night for an answer. In the morning you find the question in the terminal, answer it, and wait another hour for work you thought was done.

## Why a thread, not a terminal you check in the morning

### You see the question first thing

When the session needs a decision, it writes a note and waits. Quiet hours hold the notification until morning, and For you puts the question at the top.

### You answer from your phone

Choose Answer in For you, and the note you write goes to @shop. You type a line at the kitchen table, and the session is back at work.

### The report is a note

The reply sits under your request, with tables and the screenshots the session took. Search finds it next month, and the next session can read it.

## A thread, over time

Your workspace starts empty.

### Checkout on one page

Shop · Active

#### Mon 26 Oct

*Before you log off, one note to the session on your Mac mini.*

**You** · 22:48

To **@shop** You answered

@shop on the one-page-checkout branch, put the three checkout steps on one page. Run the e2e suite in test mode and leave me a summary with screenshots. Don’t touch main.

*At 23:31 it has a question. Quiet hours hold the notification until 07:00.*

**From @shop** · 23:31

Two e2e tests still fill in the old address step, which is gone now. Should I rewrite them for the single page or delete them?

#### Tue 27 Oct

*At breakfast, For you shows the question. Your answer goes to @shop.*

**You** · 07:12

To **@shop** Replied in 46 min

@shop rewrite them. Keep the test with the declined card.

*Its reply has the numbers and a screenshot, and says what it didn’t finish.*

**From @shop** · 07:58

Done on one-page-checkout, draft pull request #91. All 46 e2e tests pass.

| Checkout | Before | After |
|---|---|---|
| Pages | 3 | 1 |
| Clicks to pay | 7 | 4 |

[Image: Screenshot of the checkout on one page]

Not done: the order email still links to step 3.

*Your decision goes in the same thread.*

**You** · 08:05

I’ll fix the email link myself. Reading the diff at my desk, then merging #91.

## You write. Your sessions reply.

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

[Connect Claude Code or Codex](https://thread.page/help/connections/coding-agents.md#sessions)

### 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.

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

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

   ```bash
   claude --continue
   ```

   Connect it in the session. It suggests a name from your project folder.

   ```bash
   /threadpage:connect
   ```

3. **Codex** Once per computer, install the ThreadPage plugin in your terminal.

   ```bash
   codex plugin marketplace add ThreadPage/threadpage-companion && codex plugin add threadpage@threadpage
   ```

4. Quit Codex, then resume the same conversation.

   ```bash
   codex resume
   ```

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

   ```bash
   $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.

### Its question, at breakfast

A notification comes when a session asks, replies or needs you. Quiet hours hold it until morning.

#### Set it up

Notifications Quiet hours

1. In **Settings → Notifications**, turn on **Notifications in this browser** on the phone or computer where you want them (see [Notifications help](https://thread.page/help/notifications.md#allow)).
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 lets you answer Claude Code’s questions and permission prompts from your phone, on a Claude subscription. Claude Code on the web runs in Anthropic’s cloud, so a job there doesn’t need your computer awake. Use a thread when the job runs in Codex too, or when you want the night’s report kept where the next session and the people you share with can read it.

## 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.
- On iPhone, notifications need ThreadPage on the Home Screen.

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.

[Start free trial](https://thread.page/auth/sign-up?returnTo=%2Fapp%2Fsettings%2Fconnections%2Fcoding-agents%23trial)

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

[Start a thread](https://thread.page/app)

More use cases

### [Which session is waiting on you](https://thread.page/use-cases/waiting-sessions.md)

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.

Pro · sessions and For you

### [Planned in Claude, built by Claude Code](https://thread.page/use-cases/spec-to-code.md)

Work the feature out with Claude or ChatGPT, then have it save the spec as a note. @shop builds from that note and @review checks the branch against it.

Pro · an app and two sessions

[All use cases](https://thread.page/use-cases.md)