Skip to main content

Documentation Index

Fetch the complete documentation index at: https://bastani.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Atomic is an open-source CLI and TypeScript SDK that wraps Claude Code, OpenCode, and GitHub Copilot CLI in a workflow layer. You keep your coding agent — Atomic adds the structure around it: branching, retries, parallel stages, isolated sessions, controlled transcript hand-offs, human approval gates, and container-isolated execution. A workflow is one TypeScript file, versioned with your repo. Write it once, then run it across agents, repos, and teams.

Two ways to use Atomic

CLI

Pre-built autonomous behavior. Generate context files, run the Ralph autonomous loop, and launch any registered workflow from your terminal.

SDK

The @bastani/atomic-sdk library. Encode your team’s process as defineWorkflow() code and embed it in any TypeScript project or parent CLI.

Get started

Install Atomic

One-line bootstrap — no Bun or Node required — plus npm, devcontainer, and SDK-only paths.

Quickstart

Generate context files, run Ralph, and build your first workflow in a few minutes.

Why Atomic

What problem workflows solve, and how Atomic differs from a black-box harness.

Workflows

Stages, the execution graph, session isolation, and human-in-the-loop gates.

How it works

Atomic doesn’t replace your coding agent or terminal — it gives them a workflow to follow. At each stage it spawns the agent’s own CLI and talks to it through that agent’s SDK, so file editing, tool use, MCP setup, hooks, and context handling all keep working as they do today. Every stage runs inside a detachable session on a dedicated atomic socket, so runs survive terminal disconnects and can be detached, backgrounded, and reattached later.

Configuration

Atomic reads your existing .claude, .opencode, and .github configuration. Tune behavior in .atomic/settings.json and register your own workflows with atomic workflow.

Three building blocks

Atomic ships three top-level primitives. Everything else in the docs is reference material on top of these.

Workflows

Deterministic TypeScript orchestration around full coding-agent sessions. Branch, retry, fan out in parallel, pause for review.

Skills

57 structured capability modules — research, spec authoring, TDD, frontend polish, source-control helpers — auto-invoked by triggers or by /<name>.

Sub-agents

12 purpose-built agents with scoped tools and context — planner, worker, reviewer, debugger, locator, analyzer, and more.

Example use cases

Workflows you’d author with defineWorkflow — see the SDK overview:
  • Review-to-merge pipeline — review code, run CI in parallel, open a PR, notify Slack, wait for approval, merge.
  • Support ticket → draft PR — reproduce the issue, find root cause, try a fix in a sandbox, run tests, pause for review.
  • Production alert investigation — pull the failing trace, inspect recent commits, rank likely causes, draft a fix or page on-call with evidence.
  • Parallel UX testing — run persona-specific agents against the same feature, aggregate structured feedback into tasks.
  • Large migration or refactor — research, split into safe batches, run implementation + review passes, keep artifacts.

Credits

Atomic stands on the shoulders of: