Yolobox runs an AI coding agent inside a container. This can reduce access to unrelated host files. It does not protect a writable project mount from edits or deletion. Forwarded credentials and enabled host integrations also remain available to the agent.
Use the Yolobox Configurator to prepare settings. Review the resulting permissions before you launch the agent. More access is not proof of better results.
What Yolobox isolates
The project directory is mounted at its real path. The agent can use tools inside the container, including elevated container permissions. Persistent volumes can retain installed tools and session state.
The home directory is not mounted by default, but explicit mounts and integrations can change access. Review the resolved configuration for your installed release. See the Yolobox project documentation.
Do not confuse container root with a harmless process. It can still change writable mounted files. Keep a recoverable project copy before you permit broad edits.
Launch commands and explicit access
These commands select an agent or a manual shell:
yolobox claude yolobox codex yolobox gemini yolobox copilot yolobox shell
Bare yolobox can follow a configured default harness. Use the explicit shell command when that is your intent.
Check which environment variables and authentication data the selected mode passes into the container. Do not paste a production key into a configuration generator. Use a placeholder when preparing shareable examples.
Review the generated configuration
The FindUtils configurator prepares a CLI command, project TOML, and global configuration. Review each output for the installed Yolobox version. The generator does not inspect your files or enforce the configuration on your machine.
| Setting | Decision to make |
|---|---|
| Extra mounts | Which host paths are needed, and must they be writable? |
| Environment | Which values may the process read or use? |
| Exclusions | Which project files must remain unavailable? |
| Read-only project | Does the task require source edits? |
| Network access | Which downloads or external services are necessary? |
| Package customization | Which extra tools does the task require? |
| Docker access | Does the task justify access to another execution system? |
Check quoting when paths or values contain spaces and special characters. A generated shell command and TOML file have different escaping rules. Validate the output before you run it.
Use yolobox config to inspect the resolved settings. Compare them with your intended permissions. Consult the version's configuration reference if a generated field differs.
What a container does not protect
A container reduces one set of access risks. It does not remove these risks:
- A writable project mount allows changes to the host project.
- A forwarded token grants the token's actual permissions.
- Network access can permit outbound requests and data transfer.
- Docker or other host integrations can expand access substantially.
- Persistent state can retain tools, sessions, or unwanted changes.
- Runtime vulnerabilities can weaken the isolation boundary.
Start with the permissions required for the task. Use short-lived, limited credentials where available. Keep production credentials outside the agent's environment.
Review the project diff and run the applicable checks after the agent finishes. Inspect dependency and configuration changes as carefully as application code. Container isolation does not prove that the generated patch is correct.
A practical review sequence
- Identify the files the task may change.
- Keep a recoverable copy or commit of the starting state.
- Review project mounts and exclusions.
- Review credentials and external service access.
- Limit network access to what the task requires.
- Run the task with the selected permissions.
- Review the resulting changes and test the project.
- Review persistent state before you reuse the environment.
For dependency installation, the dnpm Configurator prepares a separate npm container workflow. Check its generated settings and limits. Neither configurator certifies that arbitrary code is safe.
Tools Mentioned in This Post
- Yolobox Configurator -- visual config generator for yolobox AI sandbox
- dnpm Configurator -- secure Docker-wrapped npm configuration generator
- Chmod Calculator -- calculate Unix file permissions for container mounts
Frequently asked questions
Is the mounted project protected from deletion?
A writable mount is not. Use an appropriate read-only mode for inspection tasks. Keep recovery available for tasks that must edit the project.
Does an unmounted home directory protect every secret?
No. A project can contain secrets, and the runtime can forward credentials. Review files, mounts, and environment settings separately.
Does the configurator start a container?
No. It prepares configuration text. You review and apply that text in your own environment.
Should I enable Docker access for every task?
No. Enable it only when the task requires it and you accept the expanded permissions. A nested execution interface changes the isolation assumptions.
What happens to tools between sessions?
Yolobox can retain tools and sessions in persistent volumes. Review this state when you change projects, credentials, or trust assumptions.
Where do I check supported runtimes and installation steps?
Use the installed release's official documentation. Verify the runtime requirements for your operating system before installation.
