[jhomra21]

Problem

While a Factory Droid parent runs subagents in the background, the web sidebar and the mobile thread list show only the parent. The working subagents can't be opened from the list. A subagent that hasn't started its provider run also reads as idle, because its shell status comes only from runs.

Change

• isThreadListed in packages/client-runtime/src/state/subagentDisplay.ts lists a subagent whose provider is Factory Droid while its runtime status is starting, running or waiting. It checks the provider's driver kind, so renamed instances work. A settled Droid subagent, and every other provider's subagent, stays nested under its parent as before.
• The web sidebar (Sidebar.logic.ts, Sidebar.tsx, useSidebarProjectGroups.ts, routeReveal.ts), the command palette's thread list (CommandPalette.logic.ts) and the mobile thread list and ordering (threadListV2.ts, thread-order.ts) all use that rule, so the lists match. Each caller passes the environment's provider list, which clients already load, so no wire change is needed.
• ProjectionStore.ts uses a subagent's run-less root_turn node for its status until the subagent has a run. This covers both threadShellFromProjection and the SQL shell query, and the live-shell index now includes those threads. The SQL lookup goes through the existing (thread_id, run_id) index on projection nodes.
• shellRuntime in models.ts keeps that status instead of returning no runtime for a thread without a run.

Scope and approval

This depends on the native Factory Droid provider PR and falls under the same Ideas discussion. (Ideas discussion: pingdotgg#27369) It changes which threads the sidebar lists, so it needs that approval.

Against the provider branch, the diff is 20 files: the visibility rule and run-less status in client-runtime, the web sidebar and command palette, the mobile thread list and ordering, and the projection store, with their tests. Showing a subagent's reported effort in its hover card is a separate PR.

Verification

• vp env exec --node 26.12.1 -- vp test run apps/web/src/components/Sidebar.logic.test.ts packages/client-runtime/src/state/entities.test.ts apps/server/src/orchestration-v2/ProjectionStore.test.ts apps/mobile/src/features/threads/threadListV2.test.ts: 191 passed. The tests cover listing only working Droid subagents, a Droid instance with a custom ID, a non-Droid instance whose ID contains "droid", settled subagents, and run-less status in both memory and SQL shells. The mobile ordering and action tests passed another 43.
• Typecheck of client-runtime, web, mobile and server: passed.
• vp env exec --node 26.12.1 -- vp run check:changed: format, lint, knip, GraphQL, typecheck of 37 packages and React Compiler checks passed. Its tests had one failure, a provider-droid symlink test that needs Windows symlink permission (EPERM), and browser tests couldn't start because Playwright Chromium isn't installed here.
• After merging upstream main c8a606c7b7, which also changed ProjectionStore.ts, the apps/server typecheck passed and ProjectionStore.test.ts passed 45 tests.
• Mutation checks on the pre-merge branch: removing the isThreadListed filter made lists only active Droid subagents list a settled Droid child and an active Codex child. Removing the run-less status made memory shells use run-less subagent root activity read idle instead of running.
• Not checked: browser tests (Playwright Chromium isn't installed on this machine), the native mobile app, and an integrated pass in a real client after the merge.

These screenshots predate the upstream merge. "Before" ran on the provider branch, and "after" on a fork branch that includes this change. A Droid parent starts subagents in the background.

Before: only the parent is listed while its subagents work	After: the working subagents are listed, and the parent waits on them

Built with Claude Opus 5.5 orchestrating GPT-6 Luna workers through Factory Droid in T3 Code. Upstream preparation by GPT-6.1 Terra and GPT-6 Luna, orchestrated by Claude Opus 5.5, through Factory Droid in T3 Code.

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for ab1a695.

This comment will update automatically after the next completed run.