manage-mounts

Configure host directory mount allowlists for NanoClaw agent containers.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill manage-mounts-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-mounts
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/.claude/skills/manage-mounts
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill manage-mounts-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? NanoClaw agent containers run isolated from the host filesystem, so you must explicitly control which host directories they can read or write. This Skill manages the mount allowlist at ~/.config/nanoclaw/mount-allowlist.json so you can view, add, or remove directory access without hand-editing JSON. ## Core Features & Use Cases - View Current Mounts: Display the existing allowlist showing which directories are allowed and whether each is read-only or read-write. - Add Directories: Validate paths exist, choose read-only or read-write access, and write the updated config through the setup CLI. - Remove or Reset Entries: Trim specific entries from the allowlist or reset it to empty entirely. - Use Case: You want an agent container to access your ~/projects folder as read-write while keeping ~/documents read-only. This Skill builds the correct JSON config and applies it via the setup command. ## Quick Start Ask the assistant to show the current mount allowlist and add a new directory with read-only access for NanoClaw agent containers.

Frequently Asked Questions about manage-mounts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I allow a NanoClaw agent container to access a host directory?

Add the directory to the mount allowlist at ~/.config/nanoclaw/mount-allowlist.json by running the setup CLI with --step mounts and a JSON payload listing allowedRoots. Choose allowReadWrite true for write access or false for read-only.

How do I view the current container mount allowlist?

Read the file ~/.config/nanoclaw/mount-allowlist.json with cat. It lists each allowed directory path and whether it is read-only or read-write. If the file does not exist, no allowlist is configured.

Do mount allowlist changes require a service restart?

No full restart is needed because the allowlist is read fresh each time a container is spawned. To apply changes to a group with an already running container, restart just that group with ncl groups restart --id <group-id>.

How do I remove a directory from the mount allowlist?

Read the current config, remove the unwanted entry from allowedRoots, and rewrite the trimmed JSON through the setup CLI using --step mounts --force. You can also reset everything to empty with the --empty flag.

Should container mounts be read-only or read-write?

Read-only (allowReadWrite: false) is the safer default and should be used unless the agent genuinely needs to modify files. Read-write access lets the container change host directory contents, so grant it only when required.