Profiles

Profiles define how sandbox environments are provisioned and constrained.

The source of truth lives in muthr-specs; muthr init deploys those assets into ~/.config/muthr/.

Common profiles

Profile	Best for	Network	Pre-baked image
base	Minimal testing, debugging	full	Yes
opencode	Daily coding agent sessions	full	Yes
hermes-agent	Research and custom agent workflows	restricted	Yes

How profile apply works

When you run:

muthr sandbox shell --profile <name>

muthr will:

1. ensure project container exists/runs
2. prepare baseline packages and user mapping
3. copy profile provision script + shared lib into container
4. inject runtime env contract (MUTHR_INFERENCE_URL, MUTHR_MODEL_NAME, etc.)
5. execute provisioning script as container user muthr

Provision state is fingerprinted in profile tooling so unchanged environments can skip expensive reinstall paths.

Golden images

For faster cold-start or partially offline use:

muthr image build --profile hermes-agent

Then subsequent profile starts can use the pre-baked image path instead of re-provisioning from scratch.

---

See also: Concepts · Sandbox Architecture · Troubleshooting