Repository navigation
chore: drop the fork's non-sandbox changes to T3 Code - #75
Merged
t3-code-sandboxes[bot] merged 5 commits intoNov 15, 2026
Merged
t3-code-sandboxes[bot] merged 5 commits into
t3-code-sandboxes[bot] merged 5 commits into
Conversation
Upstream shells have no latestAction. Remove the field from the contract, the server's lookup and label helper, the subagent shell refresh on finished tools, and the client overlay, so shells and the shell stream match upstream. Fork migration 004's index stays so existing fork databases keep their migration history; nothing reads it now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream's delegate_task has no `group`. Remove it from the tool input, the start-subagent commands and the subagent record, so the tool schema is upstream's plus only the sandbox target and `concurrency_full`. Stored subagent records that carry a group still decode; the extra key is ignored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream answers a child's secret request in the child's thread. Remove the fork's copy of waiting child secret cards above the coordinator's composer on web and mobile. A child started on its own sandbox by delegate_task never reached it anyway: its sandbox is linked to the host server, not paired with the client, so the client could neither list nor answer that child. The shell stream already publishes a child's secret and link cards upstream. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Remove the fork's late-timer wake detector so web and desktop clients notice a computer waking from sleep through upstream's own wakeups only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The fork made every "work locally" resend wait for the operate scope on the draft's machine, a gap only a freshly paired sandbox has. Other drafts now resend exactly as upstream does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Base automatically changed from
fix/sandbox-starting-label
to
feat/sandbox-environments
November 15, 2026 21:16
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.
Stacked on #74.
Problem. The fork should behave exactly like upstream T3 Code except for running chats on sandboxes. After the upstream sync (#73), it still carried general features and behavior changes that have nothing to do with sandboxes.
Fix (one commit each; compared against upstream 51cdf23, the commit #73 merged).
ShellStream.tsmatches upstream again. Fork migration 004 (an index) stays with a note that it is unused. The field was computed, never stored.delegate_taskgroup: removedSubagentGroupand its copies in the contracts, Orchestrator, OrchestratorMcpService and RemoteDelegation. The tool schema is now upstream's plustarget.sandboxandconcurrency_full, which sub-sandboxes need. Stored subagent records withgroupstill decode, since extra keys are dropped.agentContextBudget.json: 50013 → 49938.turnItemCanChangeUserWait, and top-level sandbox chats keep their bridgerequestSecret.suspendWakeups.ts;connection/platform.tsmatches upstream.waitingMessageCanResend: the extra wait for the operate scope now applies only to drafts on a sandbox. Other drafts resend exactly as upstream.Kept on purpose: the t3code-diy build (needed to install the fork next to official T3), the read-only milestone leftovers (existing databases hold those events), the steer secret-card fix,
outboundHttp.ts, and sandbox infrastructure and hooks.Test plan
vp run check:changed origin/fix/sandbox-starting-label: format, lint, knip, graphql, typecheck (42 packages), react compiler. The test step's only failures are the two Node 24 failures (Node 26 is pinned).orchestration-v2,mcpandpeer, AgentContextBudget and ForkMigrations: 3572 pass. Besides the two Node 24 cases, FoundationPersistence "replays and reads a log the removed milestones feature wrote" also fails on the base.ChatView.logicgains a non-sandbox resend case. client-runtime threadRequests and threadShell, web connection and ChildThreadApprovals pass.mcp-tool-useeval free modes (--context,--dry-run). The paid run, 82 delegate_task cases, still needs an Anthropic key.Claude Opus 5.5 via Claude Code.
🤖 Generated with Claude Code