Why you'd want it
nono wraps an agent such as Claude Code, Codex or Pi in a sandbox with no daemon, container or VM, and shows the exact filesystem, network and credential access before applying it. Profiles for common agents are pulled from the nono registry and can be extended into an editable JSON profile. Tools the agent calls, such as git, gh, curl or kubectl, can run in their own command sandboxes with separate filesystem and network policy, and credentials reach them through a proxy that can filter by HTTP method and path.
Best for
- Sandboxing Claude Code, Codex or Pi locally
- Scoping credentials to one tool
- Sharing reviewed agent profiles with a team
Use it when
You want to run a coding agent on your own machine with explicit filesystem, network and credential limits, without setting up containers or VMs.
Skip it if
You want VM or container isolation; the README says nono runs with no daemon, container or VM. APIs may still change before 1.0, and Windows is supported through WSL2. It runs agent commands and brokers credentials, so review a profile's grants before pulling it from the registry.
Editor's note
Other install routes (install script, Nix, Debian, Fedora, Arch) are listed in the README and at nono.sh/docs.