Repository navigation
fix(web): sending in a sandbox chat no longer swaps its history - #37
Merged
OmarAlex24 merged 1 commit intoNov 13, 2026
Merged
Conversation
A sandbox chat lists as one of two threads, the host's mirror and the sandbox's own, which keep different histories. ChatView moved the route to the other one as soon as the user was at the end with an empty composer. A send on the mirror empties the composer, scrolls to the end and resumes the sandbox, whose own thread then lists, so the view jumped to a different conversation right after the send. Typing while reading back moved it too. The redirect now waits while the user reads back, typing or not, and never moves a thread the user sent in since opening it. A stopped sandbox's own thread that stays on screen this way still resumes the sandbox from this client when it sends. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
In a sandbox chat, sending a message made the history vanish and the view jump to the bottom of a different-looking conversation.
Change
A sandbox chat shows one of two threads, the host's mirror or the sandbox's own, with different histories. ChatView moved to the other one whenever the user was at the end with an empty composer, which is exactly the state after a send. It now never moves while the user reads back, typing or not, and never moves a thread the user sent in since opening it.
Scope and approval
Requested by the fork owner in a T3 Code session. Part of stack pingdotgg#43 on
feat/sandbox-environments; each PR is one fix and builds on the one below it.Verification
sandboxThreads.test.tsvp run check:changed omar/feat/sandbox-environmentspasses format, lint, knip, typecheck (42 packages) and react compiler; 582 of 583 tests pass, and the one failure (tailscaleScriptinsandboxSetup.test.ts) fails the same way on the base branchNot yet run in a real client; UI before/after captures will follow once the stack is installed.
Model and harness: Claude Opus 5.5 (implementation subagents at high effort, coordinated by Claude Opus 5.5) in Claude Code, running in T3 Code.
🤖 Generated with Claude Code