Start sandbox provisioning on session create#880
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
nicoalbanese
marked this pull request as ready for review
May 15, 2026 09:14
nicoalbanese
changed the title
nicoalbanese
changed the title
This was referenced May 31, 2026
Closed
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
1 participant
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.
Summary
Why
New sessions should begin workspace setup before the first chat turn needs the sandbox. That reduces first-message latency while preserving a fallback path where chat runtime waits for the background provisioning run when setup is still in progress.
Notes
The follow-up commit fixes concurrency edges from review: stale run IDs are cleared only by their owner, and provisioning no longer marks a session active if archive finalization wins the race.
Validation