Non-interactive use
Atomic’s session engine supports three non-interactive entry points. Use the table below to choose one, or embed the engine with the 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.
If a text response reaches the model’s output token limit, print mode keeps the partial text on stdout, writes a truncation warning to stderr, and exits with code 1. Check the exit code before treating redirected output as complete.
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 so another process can send prompts, answer prompts, and receive events. Use it for editors, bots, and long-running services that need more than a single request/response. 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.