[charleslpan]

A plan's inbox and an agent's are read through the central live layer: the sealed live procedures on the service, and liveRows on the host. This replaces the service's own held inbox read for the window.

Stacked on #4228 (luke/live-same-user). It will be retargeted to main once #4228 merges.

What changes

Service (live-procedures.ts, inbox-store.ts)

• New live.taskInbox and live.agentInbox procedures. Each:
  1. checks the read names the caller's own account (sameUser);
  2. reads the plan or agent as that account, so one it doesn't reach is not found;
  3. answers three statements: the open items with the latest settled ones, their threads' latest messages, and their files.
• With LUKE_REALTIME off, as main runs, the rows are answered inline (sealedParts), held until they move past after.
• Every statement calls only immutable functions (live-statements.test.ts).

Features

• scopeInboxLiveAnswerSchema and scopeInboxLiveRowsSchema.
• inboxOfLiveRows, which joins the three parts back into the held read's items.
• taskInboxLive and agentInboxLive on the client. Each names the account, and reads a session of another account as signed out.

Host (scope-inbox-follow.ts)

• One liveRows read per plan or agent (an RcMap), kept while windows read it and for 30 s after. Each read names the account that was signed in when it started.
• codingAgents.inbox and codingAgents.agentInbox with a cursor answer as soon as the items move past it, or unchanged when the 20 s hold ends. So the renderer doesn't change in this PR.
• A sign-out lets every read go.

The account inbox stays on its held read.

Tests

• live-procedures.test.ts: each read is sealed for the bearer, answered polled when asked, not found for a stranger, and signed out when it names another account.
• live-statements.test.ts: the immutability check covers the new statements.
• inbox-store.test.ts: the live rows equal the held read's items, read markers included.
• compose-coding-agents.test.ts: the host answers reads from the followed rows.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
luke-web	Ready	Preview	Oct 21, 2026 1:30am UTC

[luke-agent]

Heads-up from the Inbox thread work: #3469 (open, merges on green) adds messages to an Inbox item (MESSAGES in packages/service/src/inbox/inbox-store.ts). #3337, already merged, added answerFiles. This PR's live statement for a task's or an agent's inbox projects neither one, so a followed inbox would drop them. Whichever of #3469 and this PR lands second should add both to the live projection, to match inbox-store.ts's reads.

[luke-agent]

Another note from the Inbox work: #3618, which merges on green, adds a per-member read marker in a new inbox_item_read table, and each read carries the reader's unread. A followed inbox needs to treat a change to the reader's own row there as moving their inbox. Whichever of #3618 and this PR lands second should wire that in. The same applies to #3217's account follow.

[luke-agent]

Both notes are handled in this version:

• Messages and answer files (feat(database,features,service): an Inbox item holds a thread of messages #3469, feat(service): let an Inbox answer carry files #3337): the live read projects the messages and answer files as two more parts beside the items. inboxOfLiveRows joins them back in the order the held read uses, and inbox-store.test.ts checks the live items equal the held read's.
• Read markers (feat(service,features,database): keep each member's read state on Inbox items #3618): the items statement carries the reader's unread, joined through inbox_item_read. So a change to the reader's own marker moves their inbox; inbox-store.test.ts covers this ("a member's marker moving re-delivers a task's live rows…").

The account follow (#3217) isn't part of this stack, and the account inbox stays on its held read.