Atomic’s configuration lives inDocumentation Index
Fetch the complete documentation index at: https://bastani.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
settings.json. Two locations are supported, resolved in this order:
- Project-local —
.atomic/settings.jsonin the current repo. - Global —
~/.atomic/settings.jsonin your home directory.
providers and workflows.
Example
Top-level fields
JSON Schema URL for editor autocomplete. Set to
https://raw.githubusercontent.com/flora131/atomic/main/assets/settings.schema.json.Config schema version. Currently
1.Source control provider. On every
atomic chat / atomic workflow startup, Atomic reconciles the GitHub and Azure DevOps MCP servers across agent configs — .claude/settings.json (disabledMcpjsonServers), .opencode/opencode.json (mcp.<server>.enabled), and --disable-mcp-server <name> on Copilot CLI. sapling disables both servers everywhere. These servers are disabled by default to avoid consuming tokens on projects that don’t need them.Per-provider overrides keyed by
claude, opencode, or copilot. Each value supports:chatFlags—string[]. Replaces the provider’s default chat flags entirely when set.envVars—Record<string, string>. Merged on top of provider defaults; user values win on conflict.
Custom workflow registry. Each key is the alias the
atomic CLI exposes; each value points at an external entry that calls hostLocalWorkflows([wf]). See registering workflows.Each entry supports:command—string(required). Executable to spawn (e.g.bunx,node, an absolute path).args—string[]. Static arguments prepended before Atomic’s hidden subcommands. Defaults to[].agents—("claude" | "opencode" | "copilot")[](required). Atomic registers one entry per agent listed.
atomic workflow refresh after editing.providers example
Override Claude Code’s model and max output tokens for this project only:
chatFlags is a full replacement — set it only if you need to replace defaults wholesale. envVars is merged, so you can add one variable without touching the rest.
Model selection and reasoning effort are managed by each underlying agent CLI (e.g. Claude Code’s
/model), not Atomic. Atomic’s chat command spawns the agent’s native TUI — use the agent’s own controls when interactive.Refreshing custom workflows
After editing theworkflows map or any registered workflow file:
atomic chat session it auto-defaults to JSON. See registering workflows for diagnostics.
CLI helper
For simple fields you can useatomic config set: