manage-mounts

Configure host directory access for NanoClaw agent containers via an allowlist.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Bartunek/nanoclaw --skill manage-mounts-bartunek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-mounts
Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/manage-mounts
Command: npx skills add https://github.com/Bartunek/nanoclaw --skill manage-mounts-bartunek

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.

Core Features & Use Cases

  • Show Current Config: Display the current mount allowlist and whether non-main agents are read-only.
  • Add Directories: Validate path existence and set read-only/read-write for non-main agents; update JSON config accordingly.
  • Remove Directories: Remove entries from the allowlist and persist changes.
  • Reset to Empty: Clear the entire allowlist.
  • After Changes: Restart the service to apply new mounts configuration.

Quick Start

Run the manage-mounts unit to view, add, or remove host directory access permissions.

Frequently Asked Questions about manage-mounts

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

FAQPage Schema
How do I control which host directories my agent containers can access?

You can control host directory access for agent containers by configuring a mount allowlist file located at ~/.config/nanoclaw/mount-allowlist.json, which determines readable or writable paths for main and non-main agents.

Can I set read-only or read-write permissions for non-main agent containers?

Yes, you can set read-only or read-write permissions for non-main agent containers by adding directories to the mount allowlist configuration file and validating path existence before applying the changes.

What's the best way to manage container access to host directories without security risks?

Using a mount allowlist is the best way to manage container access securely, as it validates host path existence and explicitly defines which directories are readable or writable before changes are applied.

How do I add or remove host directories from the mount allowlist?

To add or remove host directories from the mount allowlist, use the CLI workflow to validate paths, update the JSON configuration file, and then restart the service to apply the new mounts configuration.

Why are my mount allowlist changes not applying to the agent containers?

Mount allowlist changes require a service restart to apply the new configuration to agent containers, ensuring a deterministic setup by orchestrating the CLI workflow and persisting updates to the JSON file.

Can I reset the mount allowlist to empty to block all host directory access?

Yes, you can reset the entire mount allowlist to empty to clear all entries and block host directory access for agent containers, then restart the service to enforce the cleared configuration.