agents / openhands

Stonewall for OpenHands CLI

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

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

• Binaries: openhands (a standalone binary or a uv tool install with an absolute-path shebang, so no interpreter is needed).
• Readable paths: ~/.local/share/uv, where uv tool install places the Python environment openhands runs in.
• Writable paths: ~/.openhands, where agent settings including the LLM API key, MCP config, CLI preferences, prompt history and conversations live.

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

Related Policies

The OpenHands 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 openhands

Or alias it in your bash / zsh profile:

alias openhands="stonewall openhands"