agents / vibe

Stonewall for Mistral Vibe

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

It covers only what Mistral Vibe needs to start and authenticate:

• Binaries: vibe and security (macOS keychain, used for API keys).
• Readable paths: ~/.local/pipx and ~/.local/share/uv, where pipx or the uv-based installer place the Python environment vibe runs in.
• Writable paths: ~/.vibe, where config, .env (API key fallback), sessions, logs, agents, prompts and skills live.

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

Related Policies

The Mistral Vibe 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 vibe

Or alias it in your bash / zsh profile:

alias vibe="stonewall vibe"