manage-mounts

Configure host directory mount allowlists for NanoClaw agent containers.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill manage-mounts-rosedwayane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-mounts
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/manage-mounts
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill manage-mounts-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? NanoClaw agents run in isolated Linux containers, so by default they cannot see your host filesystem. This Skill manages the mount allowlist at ~/.config/nanoclaw/mount-allowlist.json so you can control exactly which host directories agent containers may access, and whether non-main agents get read-only access. ## Core Features & Use Cases - View Current Mounts: Read and display the existing mount allowlist in a readable format showing allowed directories and read-only settings. - Add or Remove Directories: Validate paths, choose read-only behavior for non-main agents, and write updated config through the setup CLI with --force. - Reset and Apply: Clear the allowlist entirely and restart the launchd or systemd service so containers pick up the new configuration. - Use Case: You want your agent to read files in ~/Documents/projects but not modify them. Add the path with read-only enabled for non-main agents, then restart the service. ## Quick Start Ask the assistant to show the current mount allowlist and add a specific host directory with read-only access for non-main agents.

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 --force and a JSON payload containing the path in allowedRoots. Restart the service afterward so containers pick up the change.

How do I view the current container mount allowlist?▼

Read the file at ~/.config/nanoclaw/mount-allowlist.json with cat. It lists allowedRoots with their paths and readOnly flags, plus blockedPatterns and the nonMainReadOnly setting.

Can I make mounted directories read-only for some agents?▼

Yes. Each allowedRoots entry accepts a readOnly flag, and the nonMainReadOnly setting controls whether non-main agents get read-only access by default. Set these when writing the config through the setup CLI.

Why don't container mount changes take effect immediately?▼

Containers read the allowlist at startup, so you must restart the service after editing the config. On macOS use launchctl kickstart with the launchd label; on Linux use systemctl --user restart with the systemd unit name.

How do I remove all directory mounts from agent containers?▼

Run the setup CLI with --step mounts --force --empty to reset the allowlist to empty. Then restart the service so running containers drop access to previously mounted host directories.