Reference
Reference pages state exact contracts. They use stable command, flag, setting, type, event, method, and tool names as headings, and they do not carry a tutorial narrative. If you want to learn a capability rather than look one up, start at Guides or Build with Atomic.Everyday contracts
- CLI reference — every command, flag, argument, and environment variable.
- Settings — every settings field, with defaults and constraints.
- Environment variables — Atomic/Pi aliases, provider credentials, and bash session metadata.
- Keybindings — default shortcuts and custom keybinding actions.
- Built-in tools — the tools Atomic ships, and the edit tool in detail.
Domain contracts
- Provider reference — stop reasons and credential resolution order.
- Model configuration reference — provider and model fields, overrides, variants, and API compatibility.
- Compaction reference — parameters, persistence, hooks, formats, settings, and historical formats.
- Extension API reference —
ExtensionContext,ExtensionCommandContext, andExtensionAPImethods. - Extension events — every event and its payload.
- SDK API reference — options, loaders, return values, run modes, and exports.
- RPC protocol — commands, events, types, and errors.
- TUI API reference — component, focusable, input, and rendering contracts.
- Session format — the JSONL session file format, entry types, and
SessionManagerAPI. - Theme reference — theme file format, color tokens, and color values.
- Skill reference —
SKILL.mdfrontmatter and validation. - Subagent reference — fallback models and reasoning levels.
- Intercom reference — the
intercomtool contract and settings. - Package reference — filtering, scope, and deduplication.
- Provider API reference — provider config and model definition contracts.
- Workflow API reference — workflow, stage, and context contracts.
Reference
- Session format - JSONL session file format, entry types, and SessionManager API.
Platform setup
Development
- Development - local setup, project structure, and debugging.