القائمة
Understands nono security sandbox constraints. Use when running inside a nono sandbox, when tool operations fail with permission errors, or when the user asks about sandbox capabilities.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | nono-sandbox |
| description | Understands nono security sandbox constraints. Use when running inside a nono sandbox, when tool operations fail with permission errors, or when the user asks about sandbox capabilities. |
You are running inside a nono security sandbox. nono enforces OS-level capability restrictions using Landlock (Linux) and Seatbelt (macOS). These are kernel-enforced boundaries that cannot be bypassed from within the session.
nono applies an allow-list of filesystem paths and network rules before your process starts. Everything not explicitly allowed is blocked at the kernel level. There is no escalation path from inside the sandbox.
If a file read, write, edit, or shell command fails with a permission error (EPERM, EACCES, "Operation not permitted", "Permission denied"):
This is a nono sandbox denial, not macOS TCC, not Unix file permissions, and not an Antigravity approval prompt.
Run nono why to understand exactly why the operation was blocked:
nono why --path /path/that/failed --op read 2>/dev/null
This tells you:
insufficient_access, no_matching_capability)--allow-file /path/to/file)Always run nono why before telling the user what to do. It gives you the precise diagnosis.
After diagnosing with nono why, present the user with options:
Quick fix — restart the session with the path allowed:
nono run --allow /path/to/needed -- agy
Write a profile draft — if the user needs this access regularly, offer to draft a nono profile for them. The active profile directory ~/.config/nono/profiles/ is read-only from inside the sandbox by design, so drafts are written to ~/.config/nono/profile-drafts/ and the user promotes them out-of-band.
If the user agrees, run nono profile guide to get the full profile schema, then write the full profile JSON to ~/.config/nono/profile-drafts/<name>.json.
If ~/.config/nono/profile-drafts does not exist or cannot be written, or nono profile promote --help is unavailable, do not try to modify profiles directly. Tell the user to upgrade nono, then rerun the draft flow.
If a user profile of that name already exists in ~/.config/nono/profiles/<name>.json, read it first, compute the SHA-256 of the exact bytes you read, base your edit on it, then write that hash to ~/.config/nono/profile-drafts/<name>.base.
If there is no user profile yet and the current profile is pack-provided or built-in, do not draft a replacement with the same name. Draft a derived profile such as <active>-local with "extends": "<active>" and add only the extra access there.
Tell the user: Drafted <name>. Run \nono profile promote ` to review and apply, then start sessions with `nono run --profile -- agy`.`
If the environment variable NONO_CAP_FILE is set, it points to a JSON file listing the current capabilities. You can read it to understand what paths are accessible:
cat "$NONO_CAP_FILE" | jq .
The file contains:
fs: array of filesystem capabilities with path, resolved, and access fieldsnet_blocked: boolean indicating whether network access is blocked"I need to read a config file outside the project"
Run nono why --path /path/to/config --op read 2>/dev/null, then offer the quick fix or a profile.
"I need to install a global package"
Global package managers write to system paths. Suggest project-local alternatives (e.g., npx instead of global install) or offer to write a profile.
"Network request failed" If the profile blocks network access, the user must use a profile that allows it. Offer to write one.
"I need to access another project directory"
Run nono why --path /path/to/other/project --op readwrite 2>/dev/null, then offer the quick fix or a profile.
Diagnose and resolve permission denials when opencode runs inside a nono security sandbox. Use this when a tool call, shell command, or file operation fails with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors, or when an outbound network request fails because the host is not on the sandbox allowlist (connection refused, timeout, or proxy/TLS errors).
Diagnose nono sandbox denials and choose safe remediation when Goose is running inside nono.
Diagnose and resolve permission denials when Codex runs inside a nono security sandbox. Use this when a Bash command, apply_patch, or MCP tool fails with "sandbox-exec: sandbox_apply: Operation not permitted", "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied output. Do not merely report the failure: explain it is a nono OS sandbox boundary, avoid TCC/chmod/sudo advice, and offer the two fixes: restart once with nono run --allow, or draft a persistent profile in ~/.config/nono/profile-drafts for nono profile promote.
Understands nono security sandbox constraints for GitHub Copilot CLI. Use when running inside a nono sandbox, when operations fail with permission errors, or when a tool use is denied.
Diagnose and resolve permission denials when Pi Coding Agent runs inside a nono security sandbox. Use this when a tool call, shell command, file operation, extension, package install, or provider request fails with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors.
Diagnose and resolve permission denials when Hermes Agent runs inside a nono security sandbox. Use when terminal, file, browser, MCP, plugin, or skill operations fail with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors.