Expand description
Sandbox integration for bash tool execution.
When a BashSandbox is provided via
ToolContext::with_sandbox, the
bash built-in tool routes commands through that sandbox instead of
std::process::Command. The workspace directory is mounted read-write
at /workspace inside the sandbox.
The concrete sandbox implementation is supplied by the host application
(e.g., SafeClaw can provide an A3S Box–backed implementation after the
user installs a3s-box). This crate defines only the trait contract.
Modules§
- srt
- Local command sandbox backed by the
srtprocess wrapper.
Structs§
- Sandbox
Command Request - Complete request passed to sandbox implementations that support the
execution controls used by the built-in
bashtool. - Sandbox
Execution Output - Output from the extended sandbox execution contract.
- Sandbox
Output - Output from running a command inside a sandbox.
Constants§
- PROTECTED_
WORKSPACE_ DIRECTORIES - Workspace-relative directories whose contents can change the agent, repository, editor, or tool control plane.
- PROTECTED_
WORKSPACE_ FILES - Workspace-relative files that can change command discovery or repository behavior even though they are not contained in a protected directory.
Traits§
- Bash
Sandbox - Abstraction over sandbox bash execution used by the
bashbuilt-in tool.
Functions§
- is_
protected_ workspace_ path - Return whether a workspace-relative path targets protected control metadata.