feat(cloud-agents): add no-repo mode, fix session init race, enable follow-ups after cloud run#1294
Open
feat(cloud-agents): add no-repo mode, fix session init race, enable follow-ups after cloud run#1294
Conversation
…ollow-ups after cloud run
3cf0aaf to
06dd80c
Compare
tatoalo
commented
Mar 18, 2026
| const sandboxContext = this.resumeState.snapshotApplied | ||
| ? `The sandbox environment (all files, packages, and code changes) has been fully restored from a snapshot.` | ||
| : `The sandbox could not be restored from a snapshot (it may have expired). You are starting with a fresh environment but have the full conversation history below.`; | ||
| ? `The workspace environment (all files, packages, and code changes) has been fully restored from where you left off.` |
Contributor
Author
There was a problem hiding this comment.
felt cleaner but can revert it tho
joshsny
approved these changes
Mar 19, 2026
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
autoInitializeSession()can both callinitializeSession()concurrently, creating duplicate sessions and sending the initial prompt twice (duplicate Slack messages)readOnlyMessageand changedisRunningto be false when cloud run is terminal, blocking the editor after task completion so reverted to the fix introduced last weekChanges
initializationPromiselock to prevent concurrent session creation, withpendingEventsbuffer that replays SSE events after the session attachesend_turnon follow-ups and resumes, callrelayAgentResponse()to post the agent's reply to SlackcurrentTurnMessagestracking inSessionLogWriterwithgetFullAgentResponse()andresetTurnMessages()for accurate per-turn message extraction