pub struct SandboxConfig {
pub add_current_working_directory: Option<bool>,
pub allow_dev_tool_access: Option<bool>,
pub auth: Option<SandboxConfigAuth>,
pub enabled: bool,
pub user_policy: Option<SandboxConfigUserPolicy>,
}Expand description
Resolved sandbox configuration.
Experimental. This type is part of an experimental wire-protocol surface and may change or be removed in future SDK or CLI releases.
Fields§
§add_current_working_directory: Option<bool>Whether to auto-add the current working directory to readwritePaths. Default: true.
allow_dev_tool_access: Option<bool>Whether to auto-grant read access to tool directories discovered on PATH and in toolchain environment variables (GOROOT, JAVA_HOME, VIRTUAL_ENV, and similar), and to common developer-tool caches, config, and toolchains. Writable grants cover scratch caches, the Unix GitHub CLI cache, and Cargo’s registry, git store, and lock/tracker files. A relocated CARGO_HOME gets the same narrow split: registry and git are read-write; bin is read-only; the home root, config.toml, and credentials.toml stay ungranted. Set to false to disable every grant listed above; user-installed toolchains and caches then need explicit userPolicy.filesystem readonlyPaths and readwritePaths entries. The working directory (see addCurrentWorkingDirectory), temporary storage, session log paths, and system locations follow their own rules and stay granted. Default: true (enabled by default; set to false to opt out).
auth: Option<SandboxConfigAuth>Credential-injection capability flags.
enabled: boolWhether sandboxing is enabled for the session.
user_policy: Option<SandboxConfigUserPolicy>User-managed sandbox policy fragment merged into the auto-discovered base policy.
Trait Implementations§
Source§impl Clone for SandboxConfig
impl Clone for SandboxConfig
Source§fn clone(&self) -> SandboxConfig
fn clone(&self) -> SandboxConfig
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more