Repository navigation
fix(sandbox): a sandbox chat says it is starting the sandbox, not ACP Registry - #74
Merged
t3-code-sandboxes[bot] merged 1 commit intoNov 15, 2026
Conversation
… Registry A sandbox chat's host thread runs on the sandbox bridge, which uses the generic ACP Registry driver, so a send after the session was released read "Starting ACP Registry". It now reads "Starting sandbox". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 tasks done
Base automatically changed from
chore/sync-upstream
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 #73.
Problem. After a sandbox chat sat idle, T3 released its provider session as it does for any provider, and the next send showed "Starting ACP Registry". The host thread runs on the sandbox bridge, which uses the generic ACP Registry driver, so the label showed that internal driver name. A normal chat shows "Starting Claude" there.
Fix.
providerStartingLabel(client-runtime, used by web and mobile) labels a run on the sandbox bridge instance "Starting sandbox", the wording T3 already uses for sandboxes elsewhere. Every other provider is unchanged.Test plan
threadExecution.test.ts"labels an open run whose provider has not started a turn": a bridge run reads "Starting sandbox" (base: "Starting ACP Registry")vp run check:changed origin/chore/sync-upstreamClaude Opus 5.5 via Claude Code.
🤖 Generated with Claude Code