fix: remember sandbox state per session - #11696
Merged
Merged
Conversation
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (31 files)
Previous Review Summaries (3 snapshots, latest commit 6089b5f)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 6089b5f)Status: No Issues Found | Recommendation: Merge Files Reviewed (32 files)
Previous review (commit 7c65a33)Status: No Issues Found | Recommendation: Merge Files Reviewed (15 files)
Previous review (commit be3ae82)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (25 files)
Reviewed by gpt-5.4-2026-03-05 · Input: 195.6K · Output: 40.3K · Cached: 1.1M Review guidance: REVIEW.md from base branch |
# Conflicts: # packages/kilo-vscode/src/services/cli-backend/connection-service.test.ts
RSO
approved these changes
Jun 26, 2026
# Conflicts: # packages/kilo-vscode/tests/unit/prompt-input-connection-guard.test.ts # packages/kilo-vscode/webview-ui/src/components/chat/PromptInput.tsx
marius-kilocode
enabled auto-merge
June 26, 2026 11:55
# Conflicts: # packages/opencode/src/kilocode/sandbox/policy.ts # packages/opencode/test/kilocode/sandbox/session.test.ts # packages/opencode/test/kilocode/sandbox/state.test.ts # packages/opencode/test/kilocode/task-nesting.test.ts
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix: remember sandbox state per session
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
2 participants
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.
The sandbox toolbar currently uses an in-memory session override while new composers fall back to configuration. As a result, opening a new Agent Manager tab can appear to re-enable sandboxing, and restarting the backend can change the effective state of existing sessions.
Persist the selected sandbox state in session metadata so every existing session restores its own value across tab switches and restarts. Keep a machine-local sticky default for genuinely new sessions, update it after successful toggles, and snapshot it into session metadata before the first prompt can execute. Blank composers update this default without creating an empty backend session.
Forked and continued sessions inherit their source state, while fresh local, worktree, and tool-created sessions use the sticky default. A sessionless support endpoint keeps the blank-composer control aligned with actual filesystem and network sandbox availability.