Minimal vs nono
Choose Minimal for reproducible, declaratively scoped local sessions for Claude Code, Codex, Gemini and Pi with a supply-chain-audited toolchain; choose nono for running Claude Code, Codex and other coding agents on your own machine with kernel-enforced file and network allow-lists and brokered credentials. Minimal uses namespaces or libkrun microVM isolation and is open source; nono uses Landlock / Seatbelt isolation and is open source.
Key differences between Minimal and nono
- Isolation: Minimal uses namespaces or libkrun microVM; nono uses Landlock / Seatbelt.
- SDKs and interfaces: Only Minimal lists MCP server. Only nono lists Rust, Python, JavaScript/TypeScript and Go.
What they have in common
- Both are tools that run on your own machine.
- Both are open source.
- Both list CLI.
Minimal vs nono at a glance
| Attribute | Minimal | nono |
|---|---|---|
| What it is | Open-source CLI that runs coding agents in declarative, isolated sessions built from a minimal.toml and a from-source package catalogue, on Linux namespaces or a libkrun microVM. | Kernel-enforced OS-native sandbox for coding agents that runs each tool call in its own ephemeral sandbox, brokers credentials and keeps a tamper-evident audit chain. |
| Type | Local / OS-level | Local / OS-level |
| Isolation | Linux: unprivileged user and mount namespaces by default (local-minimald), or a libkrun microVM with --provider local-minvmd; macOS: always a lightweight Linux microVM booted by libkrun on Hypervisor.framework | OS-level sandboxing via Landlock on Linux and Seatbelt on macOS, with opt-in user, network, IPC and UTS namespaces on Linux; a supervisor launches each tool call in a short-lived sandbox with only the capabilities it needs |
| Open source | Yes (Apache-2.0) | Yes (Apache-2.0) |
| Self-host / BYOC | No / No | No / No |
| SDKs | CLI, MCP server | CLI, Rust, Python, JavaScript/TypeScript, Go |
| Cold start (vendor claim) | Not documented | Website: "zero setup and zero latency" (claim); no figures given |
| Max session | Not documented | Not documented |
| Persistence | Sessions can be attached, detached and kept running; the session workspace starts as a copy of the project files taken at activation; a /state directory can be shared across tasks via state_key | Runs on the host filesystem within allow-listed paths; rollback restores tracked files from verified snapshots |
| Snapshots / pause | Not documented / Not documented | Yes / Not documented |
| GPU | Not documented | Not documented |
| Networking | Package builds get network access only when a dependency requires it and tasks "when necessary"; session network policy is not documented | Domain filtering and API rules by HTTP method and path through a proxy that injects credentials at the boundary; the real credential "never enters the child"; block_network() in the SDKs |
| Pricing | CLI is in public beta and free to download for Linux and macOS; "Minimal for Teams" (managed hermetic builds, org-wide policy enforcement, attestation) is marked "Coming Soon" | Free (Apache-2.0); a "nolabs Enterprise" offering is mentioned without pricing |
| Free tier | Free to download (public beta) | Free |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Not documented | Not documented |
| Good fit for | Reproducible, declaratively scoped local sessions for Claude Code, Codex, Gemini and Pi with a supply-chain-audited toolchain | Running Claude Code, Codex and other coding agents on your own machine with kernel-enforced file and network allow-lists and brokered credentials |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Minimal
- You want the agent environment declared in a file next to the code and rebuilt reproducibly
- You care about supply-chain provenance of the tools inside the sandbox
- You are on Apple Silicon and want a microVM rather than a container
Reasons to choose nono
- You want kernel-enforced allow-lists around an existing coding agent without containers or VMs
- You need credentials kept out of the agent process and injected per request
- You want a tamper-evident audit trail and file rollback for agent sessions
- You are on macOS or Linux and want zero-setup enforcement
Trade-offs to check first
- Minimal: Public beta; Teams and remote execution are marked coming soon; the full source workspace does not yet build on macOS
- Minimal: Linux default sandbox uses user and mount namespaces; the libkrun microVM provider is opt-in there
- nono: OS-level sandboxing (Landlock, Seatbelt) on the host kernel rather than a VM
- nono: Pre-1.0 with APIs still stabilising
Both are worth piloting with your own image and region. See the full Minimal profile and nono profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Minimal or nono better for AI agents?
What is the difference between Minimal and nono?
Which is open source, Minimal or nono?
How do Minimal and nono isolate code?
How does Minimal pricing compare with nono?
Can you self-host Minimal or nono?
Do Minimal and nono support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Minimal vs nono. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/minimal-vs-nono/