Manage Mounts
SkillAI & modelsLets your agent view, add, or remove which host directories its containers are allowed to access.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Manage Mounts skill
About this capability
Configure which host directories agent containers can access. View, add, or remove mount allowlist entries. Triggers on "mounts", "mount allowlist", "agent access to directories", "container mounts".
What this skill tells your AI
The instructions your AI receives, as published by nanocoai/nanoclaw in .claude/skills/manage-mounts/SKILL.md and read by ahel’s review.
Configure which host directories NanoClaw agent containers can access. The mount allowlist lives at ~/.config/nanoclaw/mount-allowlist.json.
Show Current Config
cat ~/.config/nanoclaw/mount-allowlist.json 2>/dev/null || echo "No mount allowlist configured"
Show the current config to the user in a readable format: which directories are allowed, and whether each is read-only or read-write.
Add Directories
Ask which directories the user wants agents to access. For each path:
- Validate the path exists
- Ask if it should be read-write (
allowReadWrite: true) or read-only (allowReadWrite: false, the safer default)
Build the JSON config and write it:
pnpm exec tsx setup/index.ts --step mounts --force -- --json '{"allowedRoots":[{"path":"/path/to/dir","allowReadWrite":true}],"blockedPatterns":[]}'
Use --force to overwrite the existing config.
Remove Directories
Read the current config, show it, ask which entry to remove, then write the updated config through the same write path (build the trimmed JSON and pass it to --step mounts --force -- --json):
pnpm exec tsx setup/index.ts --step mounts --force -- --json '{"allowedRoots":[],"blockedPatterns":[]}'
Reset to Empty
pnpm exec tsx setup/index.ts --step mounts --force -- --empty
After Changes
The allowlist is read fresh when a container is spawned, so new mounts apply to newly spawned containers automatically — no service restart needed.
To apply the new config to a group that already has a running container, restart just that group:
ncl groups restart --id <group-id>
Signals
- GitHub stars
- 31k
- Forks
- 13k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
manage-mounts- Source
- github.com/nanocoai/nanoclaw