agents / kiro-cli

Stonewall for Kiro CLI

Stonewall runs Kiro 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 Kiro CLI, stonewall.sh provides a specific policy at https://stonewall.sh/policies/kiro-cli.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/kiro-cli.yml

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

• Binaries: kiro-cli (a native binary, no runtime needed).
• Writable paths: ~/.kiro (settings, agents, prompts, skills, steering and sessions) and ~/.local/share/kiro-cli / ~/Library/Application Support/kiro-cli (the database with login state and chat history on Linux / macOS).

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

Related Policies

The Kiro 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 kiro-cli

Or alias it in your bash / zsh profile:

alias kiro-cli="stonewall kiro-cli"