Skip to main content
.amika/config.toml lives at the root of a Git repository and declares sandbox defaults for that repository. This page is a compact lookup of every key.
For concepts, examples, validation rules, and merge semantics, see the full guides: How configuration works (precedence, multi-repo, repo-less) and the config.toml reference (field-by-field spec).
The open-source amika CLI parses only [lifecycle].setup_script and [services.<name>]. The remaining sections are applied by the hosted platform. The singular [service.<name>] is accepted as an alias for [services.<name>].

[lifecycle]

Setup and start scripts. See details.

[env]

Environment variables set inside the sandbox. See details and env vars vs. secrets. Names must be UPPER_SNAKE_CASE. DB entries override TOML entries per key.

[services.<name>]

Named services with port bindings. See details and Services. Ports 60899–60999 are reserved. Service definitions are DB-wins-all.

[sandbox]

Default sandbox settings. See details.

[filesystem]

Additional repos to clone alongside the primary repo. See details. Only the primary repo’s .amika/config.toml is applied — see multi-repo sandboxes.

repos

[agent_credentials]

Per-agent default credential (TOML only, no database layer). See details. Keys are agent kinds (claude, codex); unknown kinds are ignored.