docs: document the experimental sandbox feature - #11697
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
Previous Review Summary (commit 78d6243)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 78d6243)Status: 1 Issues Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)SUGGESTION
Files Reviewed (3 files)
Reviewed by gpt-5.4-20260305 · Input: 41.1K · Output: 4.3K · Cached: 206.9K Review guidance: REVIEW.md from base branch |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
RSO
approved these changes
Jun 26, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
…ation docs: document the experimental sandbox feature
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.
The experimental sandbox (
experimental.sandbox+experimental.sandbox_restrict_network) confines agent shell commands and file-tool writes to the project and Kilo state directories, with optional outbound network blocking. It has shipped without user-facing documentation: the Settings page's Experimental section omits it entirely, and there is no page describing enablement, behavior, or platform support.This adds a dedicated Sandboxing page under Getting Started -> Settings and wires it into the Experimental Features section and the docs nav.
What the new page covers:
.gitwrites are always denied, and the network restriction scope (model-originated shell commands + first-party HTTP tools blocked; provider/model inference traffic and local MCP servers/plugin hooks not covered)./sandboxslash command and palette command, the◆ Sandbox onindicator, and that the toggle is ephemeral and reports a reason when the backend is unavailable.KILO_BWRAP_PATHoverride and bundled-binary verification), and the Windows-not-supported caveat.The Settings index Experimental list gets a Sandbox bullet linking to the new page, and the
experimentalJSON example is extended with both keys so users see the config shape inline.