How Atomic Agent's desktop app is just a plain HTTP client to its OpenAI-compatible server

GapNew4766 · reddit · 2026-10-13

The team behind Atomic Agent (MIT-licensed) explains why its desktop app talks to the agent via a plain OpenAI-compatible HTTP server instead of the existing NDJSON sidecar: sidecar and server both boot the full runtime, so pointing them at one state directory spawns two task schedulers and cron jobs fire twice.

API highlights

Strict OpenAI subset + opt-in extensions

By default the stream is a strict subset of OpenAI's chat.completion.chunk — off-the-shelf clients like the Vercel AI SDK zod-validate every frame and break on unknown events. With X-Atomic-Extensions: 1 you get named frames: reasoningprogress, toolprogress, fusionworker (role, model, tool, step count, ETA, context tokens), steerapplied/steerundelivered, and a final usage frame.

Steering and approvals

Gotchas

Original post →

More from coding & agent

coding & agent channel →