Programmatic use

Atomic exposes three integration modes plus a component API for interactive extension interfaces. Pick one mode, complete its minimal example, then continue to its reference.

Choose a mode

You want	Use	Start at
A one-shot run whose output you parse as structured events	JSON event stream mode	`atomic --mode json`
A long-lived process you drive with commands and read events from	RPC mode	`atomic --mode rpc`
Atomic embedded inside a Node.js application, with its resources and lifecycle in-process	SDK	`@bastani/atomic`

JSON mode is the smallest surface: one process, one prompt, a stream of newline-delimited events, then exit. RPC mode keeps the process alive so you can send more input, interrupt, switch models, and answer tool permission prompts. The SDK gives you the same engine as a library, with programmatic control over extensions, skills, tools, and session storage.

Then continue to the contracts

RPC protocol — every command, event, and type.
RPC extension UI protocol — drive extension-rendered UI over RPC.
RPC client examples — additional client implementations.
SDK API reference — options, loaders, return values, run modes, and exports.

Build interactive extension interfaces

TUI components covers writing a first component and the common interaction patterns; TUI API reference holds the component, focusable, input, and rendering contracts.

Build with Atomic

Extend a session

Orchestrate work

Distribute

Models and providers