# Yolobox Orchestrator

> Use when the agent is outside yolobox and needs to start, inspect, or control yolobox sessions, choose the right yolobox subcommand or flags, read merged config, decide between scratch, readonly, docker, or network options, or debug how a yolobox launch should be configured.

- Skill: `finbarr/yolobox-orchestrator` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add finbarr/yolobox-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finbarr/yolobox-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: finbarr (https://skillmd.com/u/finbarr)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/finbarr/yolobox-orchestrator

---


# Yolobox Orchestrator

Use this skill for host-side orchestration of yolobox sessions.

Do not use it for questions about the current environment from inside a running box. Inside the container, use `yolobox` instead.

1. Start from the user's intent, then choose the smallest `yolobox` command or flag set that accomplishes it.
2. Check `yolobox config` when defaults, merged config, or flag precedence matter.
   - If `default_harness` is set, bare `yolobox` launches that shortcut; use `yolobox shell` for an explicit shell.
3. Prefer explicit isolation and safety flags:
   - `--scratch` for disposable or concurrent sessions that must not share `/home/yolo`.
   - `--readonly-project` when the agent only needs read access to the project tree.
   - `--no-env-passthrough` when host API/token environment variables should not enter the box automatically.
   - `--claude-config --no-claude-auth` when host Claude settings should be synced but the persistent box must keep its own `/login` credentials. This still live-mounts host Claude project history read/write.
   - `--open-bridge` only when the agent needs to open HTTP(S) URLs in the host browser.
   - `--docker` only when the agent needs Docker access or sibling containers.
4. When you need exact command patterns or edge-case reminders, read [references/commands.md](references/commands.md).
5. If you launch a box for another agent, point it at `yolobox` and `YOLOBOX_CONTEXT_FILE` for inside-the-box introspection.
6. When discussing concurrency, distinguish isolated per-run manifests from shared persistent state: manifests are per-run, but `/home/yolo` and `/var/cache` are shared unless `--scratch` is used.