[andrewcai8]

Syncs upstream T3 Code through f054d1b, upstream's newest commit, which has green CI. That is 114 commits (680152e..f054d1b), and 17 files conflicted.

Notable upstream changes:

• ChatView is split again: the send paths (useComposerSend), resume (useComposerResume), lifecycle actions (useThreadLifecycle), rewind, right panel and terminal actions, ComposerControlsBar and ChatBannerLane (refactor(web): the composer's layout and provider hooks live in their own files pingdotgg/t3code#23042 to refactor(web): ChatView's timeline banners render in ChatBannerLane pingdotgg/t3code#23101). Streamed reply text and visit marks no longer re-render ChatView (perf(web): streamed reply text no longer re-renders ChatView pingdotgg/t3code#23117, perf(web): visit marks during a reply no longer re-render ChatView pingdotgg/t3code#23124).
• Messages from other agents and automations fold into one-line rows (feat(web,mobile): messages from other agents fold into one-line rows pingdotgg/t3code#23135, feat: show automation messages as compact timeline rows pingdotgg/t3code#22638). Full access approvals say why Claude asked (feat(server,web,mobile): approvals in full access say why Claude asked pingdotgg/t3code#22546).
• Mobile drafts are now the root Thread route with a draft param. The NewTaskSheet navigator is gone (fix(mobile): unify draft and thread navigation and composer behavior pingdotgg/t3code#23467, fix(mobile): preserve new-thread drafts and native header layout pingdotgg/t3code#23366). Many iPhone Duo fixes.
• A Claude agent stops when the server that started it dies (fix(server): a Claude agent stops when the server that started it dies pingdotgg/t3code#23389). Abandoned turns are stopped before a thread continues (fix(server): stop abandoned turns before continuing threads pingdotgg/t3code#23169).
• Claude idle compaction has a global default (feat(claude): idle compaction has a global default and per-instance overrides pingdotgg/t3code#23037). Webhook filters take a [] array wildcard (feat(server): webhook filters fan out over arrays with a [] path wildcard pingdotgg/t3code#23282). Run duration and outcome metrics (feat(server): export how long runs take and how they end pingdotgg/t3code#22094).
• Node 26.12.1 pin, and typescript is the tsc-rs drop-in (fix(build): pin Node 26.12.1 for development and standalone releases pingdotgg/t3code#23165, chore(typecheck): typescript is the tsc-rs drop-in, no effect-tsgo patch pingdotgg/t3code#23023).

Conflicts keep upstream's change and re-apply the fork's behavior. Where upstream moved code to a new file, the fork's edit moved with it.

Web

• ChatView: the fork's cloud send code moved into upstream's useComposerSend. That is the reconnect-on-send guard and reconnectAndSend, cloud.blocksSend(), held first sends keeping their message id and time, leaseForSend, nextDraftProjectRef and claimFirstTurn. ChatView passes it canReconnectOnSend and cloud, and keeps connectionBox for the account-switch note and useProjects() for useCloudChat.
• useComposerResume sends the continuationPrompt setting (feat: configurable continuation prompt, with an account-switch note #244) instead of upstream's fixed "Continue where you left off."
• useThreadLifecycle: opening a related thread finds the environment that owns it, so a message Home sent from another machine opens the right thread.
• ChatComposer: upstream moved the model picker into ComposerControlsBar. The cloud picker's entry and list go through a new pickerInstanceId prop.
• TimelineUserMessageRow: upstream removed the "Sent by..." lines in favor of folded rows. "Watch report from T3 Code" stays on Home's watch reports. A folded message Home sent is headed "Home" instead of a thread title, and upstream's "Open thread" button replaces the fork's "Sent by Home" link.
• Sidebar: upstream's useQuietThreadShells plus the fork's homeThreadRef. SidebarThreadRow merged cleanly but imported useThreadShell twice, so the fork's copy is gone.
• ConnectionsSettings: upstream moved the add-machine dialog into AddEnvironmentDialog. The fork's balancedEnvironments line stays.

Mobile

• Stack: upstream's tree with NewTaskFlowProvider at the root. <CloudBoxesWorker /> is re-added, and NewTaskCloudMachine is now a root route (new/cloud-machine) listed as a workspace overlay.
• use-new-thread-navigation takes the layout's selectThreadRoute. Drafts open through it with a requestId, and cloud machines open the root NewTaskCloudMachine route. HomeRouteScreen, CommandPalette and AdaptiveWorkspaceLayout use it. Upstream's startNewTask goes through it too, so a project on another chat's box or on a host that runs no agents still gets a cloud machine instead of a draft the host refuses.
• NewTaskRouteScreen checks for a cloud machine before upstream's "a draft is open, go back" branch. NewTaskCloudMachineRouteScreen opens the new draft with selectThreadRoute instead of resetting a NewTaskDraft route that no longer exists, and still sends branchOptional.
• NewTaskDraftRouteScreen: branchOptional moved into upstream's thread-route-state.ts. NewTaskDraftScreen passes connectionStatusLabel to upstream's ThreadDetailScreen, and provisionedSkills now reaches the menu through ThreadComposer.
• NewTaskFlowProvider now stays mounted, so useNewTaskEnvironmentPick takes active. Box demand holds only while a draft is open, which keeps the fork's rule that boxes connect only while their chat needs them.
• ThreadArrangementSheet: upstream's safe-area rewrite with the fork's settlement environment checks re-applied.

Server

• orchestrator/tools.ts: upstream's [] filter sentence plus the fork's cloud-only scheduling sentence.
• ProviderTurnStartService.test: the harness takes both upstream's previousTurn (fix(server): stop abandoned turns before continuing threads pingdotgg/t3code#23169) and the fork's deliverTurn.
• pnpm-lock.yaml is upstream's lock re-resolved with pnpm 12.14.0 for the fork's dependencies. It is still the two-document lockfile that decodePnpmLock reads.

Upstream pingdotgg#23389 and pingdotgg#23169 against fork features. Claude now spawns through a /bin/sh watcher that stops the CLI's process group when the server dies. Restart continuation already assumes the old turn ended at restart, and the account switch and canUseTool auto-approve paths do not touch the spawn. pingdotgg#23169 only rewrites a failed run's turn that is still running on the same provider thread before continuing. The restart continuation, account switch, usage-limit, runtimeLayer and ClaudeAdapterV2 tests all pass with both changes.

Verification:

• tsc-rs --noEmit is clean for contracts, shared, client-runtime, provider-core, provider-cursor, provider-pi, provider-opencode, server, web, mobile, desktop and scripts.
• knip:check passes. vp lint has no errors and vp fmt --check is clean on every file that differs from upstream (641 TS files).
• Server: 2610 tests pass across home (forks, bunShim, ForkExec), environmentControl (ProvisionPreparation and the Modal, E2B and Namespace runtimes), provider (ProviderAccountSwitch), usage, mcp, scheduledTasks, accountRouting, runtimeLayer, RestartContinuation, ProviderContinuationService, ProviderTurnStartService, RunExecutionService, ClaudeAdapterV2, ClaudeAgentSdkQueryRunner, serverSettings, ForkMigrations and scripts/runtimeDependencies.
• Three server tests fail only on this Mac because of the /var temp symlink: two in UsageService and one in ClaudeSkills. ClaudeSkills is identical to upstream. All three pass with TMPDIR set to the resolved /private/var path.
• All contracts (149) and client-runtime (1369) tests pass. Web unit tests for the chat, cloud, settings and sidebar areas pass (667). Mobile tests for threads, home, layout, keyboard, connection, state and lib pass (1863).
• vp run --filter t3 build succeeds, and node apps/server/scripts/build-runtime-artifact.ts builds the runtime tar (67 MB, 756 entries).
• Open fork PR fix(server): a wake turn the usage limit stopped no longer cancels the thread's resume #250 merges onto this branch without conflicts.

Not verified: the web, desktop and mobile UI were not run. The cloud send paths now in useComposerSend and the new mobile cloud-machine route are covered only by the typecheck and reasoning, so they need a real cloud chat on web and an iOS and Android pass.

🤖 Generated with Claude Code

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.9 KiB	0 B (0.0%)	29.3 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.2 KiB	0 B (0.0%)	29.3 KiB	✅
Claude	Live turn messages	2	2	0 (0.0%)	8	✅

Baseline: 687580e · PR result: d57e72d · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.