Non-interactive use

Atomic does not need a terminal UI. The same session engine backs three non-interactive entry points, and each one is documented in full elsewhere — this page only helps you pick.

You want	Use	Read
One prompt, one answer, then exit	Print mode (`-p`, `--print`)	CLI reference
A machine-readable stream of everything the session does	JSON event stream	JSON event stream
A long-lived session another program drives	RPC	RPC
To embed Atomic in your own TypeScript program	SDK	SDK

Print mode

atomic --print "..." runs a single turn and exits. It also reads piped stdin and merges it into the prompt, so it composes with ordinary shell pipelines. Flags, exit codes, and the stdin merge rules are in the CLI reference.

JSON events

When you need to observe a run rather than read it, the JSON event stream emits one structured record per message, tool call, and result. Use it for logging, CI annotations, or piping into another tool. The event shapes are in JSON event stream.

RPC

RPC keeps a session alive and lets another process send prompts, answer prompts, and receive events over a protocol. Use it when a single request/response is not enough — editors, bots, and long-running services. Start at RPC and the RPC protocol.

Next steps

CLI reference for every flag and exit code.
Programmatic use for choosing between the SDK, RPC, and the event stream.
Background and parallel work if the work should continue while you keep chatting interactively.