Repository navigation
Captains: a lead thread per project that launches, watches, and lands its own crew #31181
hridaya423
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When I run several threads in one project, I become the dispatcher. I start each thread, check each one, answer its questions, and merge its branch. I want one thread per project that does this for me. I hand it a task. It splits the task, launches worker threads, watches them, checks their work, and asks me only what it cannot decide.
Agents can already build most of this with the T3 MCP tools. I wrote a lead-thread skill on
t3_thread_launch,t3_thread_read,t3_thread_send,t3_pending_request, andschedule_task. On a test repo, it split one task into two orders, ran two workers in their own worktrees, reran their tests, settled both threads, and reported back in 70 seconds. Three gaps make it fragile:delegatedFromis a top-level thread withparentThreadId: null. The launcher is recorded only as the sender of the first message, so the crew scatters through the sidebar. Sidebar: show child threads nested under the thread that opened them #31157 asks for the same nesting from the user side.t3_thread_waitor poll on aschedule_taskinterval. feat(home): add Home, an agent that manages threads across your machines #15975 solved this witht3_thread_watchand watch reports. Optional compact incoming agent reports with source-thread navigation #20243 asks for compact incoming reports.t3_pending_requestanswers questions but cannot approve a permission request. A crew thread that waits for approval stays blocked until I open it.Relation to Home
Home (#15975) is one lead for the whole fleet. A captain is the same idea, scoped to one project, with several running at once. This proposal reuses Home's parts instead of competing with them. The mesh PR (#24863) already uses "captain" for the routing machine, so I expect the name to change.
Proposed scope
Each step is one small PR that is useful without the next one. I ask for approval of step 1 and for direction on the sequence.
t3_thread_launchwithdelegatedFromsetsparentThreadIdand a newrelationshipToParent: "crew". The sidebar nests crew under the lead. A user can detach a crew thread to make it top-level again.t3_thread_watch, moved to the server so that it works while the desktop app is closed.A captain role, a sidebar section for captains, and a crew board would come later, each with its own discussion.
Questions
delegatedFromlaunches, or an explicit flag?This discussion asks for direction and scope. It is not an approval.
Written with Claude Opus 5.5 in Claude Code, running in T3 Code.
All reactions