agents / kilo

Stonewall for Kilo CLI

Stonewall runs Kilo CLI inside a kernel-enforced sandbox. The agent only sees your project directory and the few binaries and paths the policy names. Everything else on your machine, from ~/.ssh to your browser profile, is invisible to it, no matter what a prompt says.

Policy

For Kilo CLI, stonewall.sh provides a specific policy at https://stonewall.sh/policies/kilo.yml. You can use it by simply including it in your .stonewall.yml config, or using the CLI:

stonewall policy include https://stonewall.sh/policies/kilo.yml

It covers only what Kilo CLI needs to start and authenticate:

• Binaries: kilo, kilocode (the same command under its second name) and node (runs the launcher script of the npm package).
• Readable paths: ~/.kilo, where global skills, agents and commands live.
• Writable paths: ~/.config/kilo (config, themes, agents), ~/.local/share/kilo (credentials and sessions), ~/.local/state/kilo and ~/.cache/kilo (state and cache).

It intentionally does not allow sh, bash, git or any other tool the agent could use to run arbitrary programs.

Related Policies

The Kilo CLI policy is meant to be combined with policies for what your project actually needs:

• base.yml: read-only file inspection (cat, grep, ls, …), hides .env and secrets.
• git-safe.yml: read-only git, no commits, no credentials.
• git-unsafe.yml: full git, including commits and push.
• A language policy for builds and tests, e.g. go.yml, python.yml or typescript.yml.

Usage

Start the agent through stonewall instead of directly:

stonewall kilo

Or alias it in your bash / zsh profile:

alias kilo="stonewall kilo"