OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Security & Sandboxing

Nono

Nono is an open-source Rust command-line tool that runs AI agents and delegated tools in configurable security sandboxes. Its profiles define filesystem access, network allowlists, credentials and tool rules, and can be extended from registry profiles.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Nono — OpenViST project profile in Agent Security & Sandboxing.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Nono when you need to launch an AI agent through a profile that defines its permitted access, or when you want to inspect and adapt those rules before using a profile.

Who it is for

  • Developers who want to constrain what an AI agent can access while it runs.
  • Agent developers who want to create, edit or publish reusable agent packages.
  • Teams that need to review and adapt agent access rules through composable profiles.

Documented uses

  • Run an AI agent with a defined filesystem and network scope.
  • Keep local credentials and files outside an agent's permitted access in a configured profile.
  • Set rules for tools an agent delegates work to.
  • Scaffold and edit a profile that extends a registry profile.
Before you choose

Requirements & limits

The project documents installation through a shell script, Homebrew and Nix, and lists macOS, Linux and Windows through WSL2. It is licensed under Apache-2.0.

  • The README describes profiles as the place to specify filesystem scope, network allowlists, credentials and tool rules.
  • The registry provides profiles for agents, while nono profile init can export an editable profile extending a selected base.
  • The README says APIs are stabilizing ahead of a 1.0 release and may still change.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Launch an agent with a registry profile

Run an agent through Nono using a profile available in its registry.

Before you start

  • Nono installed
  • An agent available to run, such as OpenCode

Steps

  1. Search the registry for an agent profile with nono search opencode.

  2. Launch the agent through Nono with nono run --profile nolabs-ai/opencode -- opencode.

Expected outcome

The README's example runs OpenCode with read/write access to the current directory and no access to the rest of the disk, SSH keys or cloud credentials.

Guide limitations

  • The described access scope is for the OpenCode registry-profile example; other profiles may specify different rules.
  • The project notes that APIs may still change as they stabilize ahead of a 1.0 release.
Documentation 1 ↗
Source-based practical guide

Create an editable profile from a registry profile

Scaffold a profile that extends a registry profile so its rules can be reviewed and adapted.

Before you start

  • Nono installed
  • A base profile, such as nolabs-ai/opencode

Steps

  1. Scaffold a profile with nono profile init opencode --extends nolabs-ai/opencode.

  2. Review and edit the exported composable JSON profile.

  3. Use the profile when launching the agent with nono run --profile opencode -- opencode.

Expected outcome

An editable profile inherits from the selected base profile and exposes filesystem, network, credential and tool rules for review.

Guide limitations

  • The README describes profile editing and a launch command but does not provide a full policy-authoring walkthrough.
  • APIs may still change as they stabilize ahead of a 1.0 release.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
nolabs-ai/nono · Official homepage title · retained in its source language
How we review sourcesSuggest a correction