container

# Aerovato Container Use this skill to help users operate the Aerovato `container` CLI. Confirm that the user means the [Aerovato Container](https://github.com/aerovato/container) sandboxing CLI command when the word "container" is ambiguous. ## Capability Boundary Treat setup and customization as host-side work. - Host-side agents can inspect and modify `~/.code-container/settings.json`, `~/.code-container/Dockerfile.User`, and `~/.code-container/configs/` with user approval. - Agents inside a managed Container normally cannot access the host-side settings or user Dockerfile. - The optional `agents-directory` tool pack mounts Container's persisted copy of `~/.agents`; it does not expose host-side Container settings. - If you suspect you're inside a Container, ask the user to run outside the container. - Never mount the complete host `~/.code-container/` directory into a managed container. - If `~/.code-container/` is missing, determine whether this is a fresh host installation or a managed Container session. Ask the user when uncertain. - If host files are inaccessible, explain the boundary and provide host-side steps instead of creating shadow configuration inside the managed container. ## Operating Rules 1. Inspect the current platform, installed version, settings, user Dockerfile, and relevant persisted configs before proposing changes. 2. Obtain approval before installing software, changing files, starting a build, accessing the network, or cloning source code un...