Repository navigation
feat(inbox): agent-launched threads go to Agents unless the agent picks an inbox - #72
Merged
nullStack65 merged 2 commits intoNov 18, 2026
Merged
Conversation
… 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>
This was referenced Nov 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Threads that an agent started through
t3_thread_launchorcreate_threadscopied 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
inbox:kameron,jeff,sharedoragents. The default isagents. The parameter description tells agents to pick a founder only when that founder asked for the thread or must act on it.inboxRoutingpatch adjusts the chosen inbox:inbox:"kameron"plus{attentionKind:"FYI"}stays in Kameron's inbox as FYI. Given alone,inboxRoutingapplies as before.inboxRoutingForinpackages/contracts/src/threadInbox.tsis now the single routing table. The thread action menu and agent launches both use it, so "Move to Kameron" andinbox: "kameron"file a thread identically.inboxRouting, notinbox. A peer on an older release therefore files them the same way.Checks
threadInbox.test.tscovers every inbox choice and the override.handlers.test.tsaddsa launch is filed in Agents unless the agent picks an inbox, which fails on the base: the handler copied the caller's inbox there.threadInbox, projecthandlers,threadActionMenu.logic,OrchestratorMcpServiceandThreadLaunchService(194 tests).vp run check:changed origin/release/native-0.1.10on the repair: format, graphql, typecheck (37 packages), tests (7 files) and react compiler pass. Lint flagged one inlineSchema.is; I hoisted it, and lint on the touched files is clean.mcpToolListJsonBytesgoes from 49,736 to 52,637. Only 672 bytes come from this change (theinboxfield on two tools). The other 2,229 bytes were already stale onrelease/native-0.1.10, which measures 51,965 without this change.INBOX_CAPABILITYexport.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.5628057864:inboxplus a partialinboxRoutingdropped the chosen inbox. The patch now applies over the inbox, andthreadInbox.test.tshas a row for it.inboxdescription now points the agent at its thread'sinbox.ownerint3_thread_read, so it can tell which founder it works for.schedule_taskgives the agent no inbox choice. Scheduled runs file in Agents and can be moved afterwards witht3_thread_update, using the route action.InboxChoiceschema instead of a cast.handlers.ts, the new handler test fails ([undefined, undefined, undefined]).Known limits
mcp-tool-usecalls paid models, and this overnight run is not approved to spend. No existing case covers inbox routing. Run one before relying on how well models pick an inbox.threadActionMenu.logic.test.tscovers.--no-verify, for the same base-branch reasons as feat(placement): bind auto-placed delegated tasks before launching anywhere #68–fix(placement): keep a draft whose send failed on the machine it was sent to #70. The checks above were run by hand.Provenance
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".🤖 Generated with Claude Code