Hysen Labsnono
Sandbox any AI agent in seconds - zero setup, zero latency.
Nono: sandboxing AI agents in seconds
Nono drops AI agents into a sandbox in seconds with no daemon, no container, no VM, and a least privilege default you can fork and share.
The pitch in a sentence
Sandbox any AI agent in seconds, with zero setup and zero latency. Those are the claims at the top of the README, and it spells out what zero means. No daemon, no container, no VM, and no disk space used along the way. A long list of coding agents is named as supported, among them Claude Code, Codex, Pi, CoPilot, Hermes, OpenCode, and OpenClaw. The tool runs on macOS, Linux, and Windows with WSL2, and a least privilege sandbox is enforced out of the box rather than offered as an option.
Backed by the Sigstore team
The README credits the team behind Sigstore, which it calls the standard for secure software attestation. That standard is in use by PyPI, npm, brew, and Maven Central. The lineage is worth mentioning because it sets expectations. The sandbox work comes from people who have already shipped security infrastructure that much of the packaging world depends on, which lends some weight to the isolation claims that follow.
What to expect before 1.0
The project still feels like it is settling into place. Ahead of a 1.0 release the APIs are stabilizing, with changes kept to a minimum. The registry namespace has moved to nolabs-ai, and migration instructions cover updating references and removing old packs. On the configuration side, you can fork the default config, tweak it, theme it, and share it with a team or the community through the registry. Sandbox behavior plus a shareable config is what most of the README spends its time on, and that combination is the part that is likely to keep people coming back.
Community notes