Skip to content

feat(inbox): agent-launched threads go to Agents unless the agent picks an inbox - #72

Merged
nullStack65 merged 2 commits into
release/native-0.1.10from
feat/agent-launch-inbox-choice
Nov 18, 2026
Merged

nullStack65 merged 2 commits into
release/native-0.1.10from
feat/agent-launch-inbox-choice

Conversation

@nullStack65

@nullStack65 nullStack65 commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Threads that an agent started through t3_thread_launch or create_threads copied the calling thread's inbox routing. So any agent working in a thread in Kameron's inbox filled that inbox with its child launches. Kameron asked that agent-started threads stop cluttering his inbox, and that the launching agent choose where they go.

Fix

  • Both launch tools take an optional inbox: kameron, jeff, shared or agents. The default is agents. The parameter description tells agents to pick a founder only when that founder asked for the thread or must act on it.
  • An inboxRouting patch adjusts the chosen inbox: inbox:"kameron" plus {attentionKind:"FYI"} stays in Kameron's inbox as FYI. Given alone, inboxRouting applies as before.
  • inboxRoutingFor in packages/contracts/src/threadInbox.ts is now the single routing table. The thread action menu and agent launches both use it, so "Move to Kameron" and inbox: "kameron" file a thread identically.
  • Delegated launches to a linked environment send the resolved inboxRouting, not inbox. A peer on an older release therefore files them the same way.
  • Web-client launches, CLI launches and delegated subagent threads are unchanged. The client attributes its own launches to the chosen founder, the CLI never copied a caller's inbox, and subagents stay children.

Checks

  • threadInbox.test.ts covers every inbox choice and the override. handlers.test.ts adds a launch is filed in Agents unless the agent picks an inbox, which fails on the base: the handler copied the caller's inbox there.
  • Focused suites pass on Node 26.13.1: threadInbox, project handlers, threadActionMenu.logic, OrchestratorMcpService and ThreadLaunchService (194 tests).
  • vp run check:changed origin/release/native-0.1.10 on the repair: format, graphql, typecheck (37 packages), tests (7 files) and react compiler pass. Lint flagged one inline Schema.is; I hoisted it, and lint on the touched files is clean.
  • Context budget: mcpToolListJsonBytes goes from 49,736 to 52,637. Only 672 bytes come from this change (the inbox field on two tools). The other 2,229 bytes were already stale on release/native-0.1.10, which measures 51,965 without this change.
  • knip fails on the base too, and this PR does not touch those findings: four unused scripts, plus the unused INBOX_CAPABILITY export.

Review round (the PR's one bot round)

Independent Claude Opus 5.5 review of 2501681651, run through T3 delegation because CodeRabbit is disabled for this base. Nothing blocking.

  1. Medium, fixed in 5628057864: inbox plus a partial inboxRouting dropped the chosen inbox. The patch now applies over the inbox, and threadInbox.test.ts has a row for it.
  2. Low, fixed: the inbox description now points the agent at its thread's inbox.owner in t3_thread_read, so it can tell which founder it works for.
  3. Low, follow-up, not in this PR: schedule_task gives the agent no inbox choice. Scheduled runs file in Agents and can be moved afterwards with t3_thread_update, using the route action.
  4. Nit, done: the thread menu checks inbox actions with the shared InboxChoice schema instead of a cast.
  5. Nit, verified: with the base handlers.ts, the new handler test fails ([undefined, undefined, undefined]).

Known limits

Provenance

  • Model: claude-opus-5-5 (Claude Opus 5.5). It continued a Codex WIP handoff from Kameron's laptop thread "Route Agent Threads to Team Inboxes".
  • Harness: Claude Code in T3 Code, on ASUS.

🤖 Generated with Claude Code

nullStack65 and others added 2 commits November 18, 2026 10:34
… picks an inbox

t3_thread_launch and create_threads copied the calling thread's inbox
routing, so any thread an agent started from a founder's thread landed in
that founder's action inbox. Both tools now take an `inbox` choice
(kameron, jeff, shared, agents) that defaults to agents. Explicit
`inboxRouting` still wins. The thread menu and agent launches share one
routing table, and delegated launches send the resolved routing so older
linked environments file them the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eplacing it

An agent that sent `inbox:"kameron"` with a partial `inboxRouting` such as
`{attentionKind:"FYI"}` lost the inbox choice and the thread landed only in
Agents. The patch now applies over the chosen inbox. The `inbox` description
points the agent at its thread's `inbox.owner`, and the thread menu checks
its inbox action with the shared InboxChoice schema instead of a cast.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nullStack65
nullStack65 merged commit 47007e1 into release/native-0.1.10 Nov 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant