manage-mounts

Configure and control host directory access for NanoClaw agent containers.

5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thmtz/nanoclaw-fleet --skill manage-mounts-thmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-mounts
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/manage-mounts
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill manage-mounts-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure which host directories NanoClaw agent containers can access. The mount allowlist lives at ~/.config/nanoclaw/mount-allowlist.json.

Show Current Config

Show the current config to the user in a readable format: which directories are allowed, whether non-main agents are read-only. To view it directly, run: cat ~/.config/nanoclaw/mount-allowlist.json 2>/dev/null || echo "No mount allowlist configured"

Add Directories

Ask which directories the user wants agents to access. For each path:

  • Validate the path exists
  • Ask if it should be read-only for non-main agents (default: yes) To update the allowlist, build the JSON config and write it: npx tsx setup/index.ts --step mounts --force -- --json '{"allowedRoots":[{"path":"/path/to/dir","readOnly":false}],"blockedPatterns":[],"nonMainReadOnly":true}' Use --force to overwrite the existing config.

Remove Directories

Read the current config, show it, ask which entry to remove, write the updated config.

Reset to Empty

npx tsx setup/index.ts --step mounts --force -- --empty

After Changes

Restart the service so containers pick up the new config:

  • macOS: launchctl kickstart -k gui/$(id -u)/com.nanoclaw
  • Linux: systemctl --user restart nanoclaw

Quick Start

Run the manage-mounts flow to add, remove, or reset host directory allowlists, then restart the nanoclaw service to apply changes.

Frequently Asked Questions about manage-mounts

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

FAQPage Schema
How do I configure host directory access for agent containers?

You can configure host directory access by modifying the mount allowlist JSON file. This specifies which host directories agent containers can access and whether they have read-only permissions.

How do I add a new directory to the mount allowlist for agent containers?

To add directories to the mount allowlist, provide the desired paths and specify if they should be read-only for non-main agents. The configuration is then written to the mount-allowlist JSON file.

Do I need to restart the service after changing the mount allowlist?

Yes, you must restart the service for containers to pick up the new mount allowlist configuration. Run the specific restart command for your operating system, such as systemctl on Linux or launchctl on macOS.

Can I set read-only permissions for specific agent containers?

Yes, you can apply read-only permissions on a per-entry basis for non-main agents. When adding a directory to the mount allowlist, you can toggle the readOnly setting for those agents.

What are the limitations of managing mounts with this approach?

This approach applies specifically to deployments on macOS and Linux. Directory paths must be validated for existence before they can be successfully added to the mount allowlist configuration.

How do I reset the container mount allowlist to empty?

You can reset the mount allowlist to empty by running the setup script with the empty flag. This clears all configured directory access for agent containers.