01
Keep the brief with the work
Scope and responsibility stay attached to the task across coding and review sessions.
One operator. Named specialists.
Build real software. Know what shipped.
ATOM is a universal plugin for AI that brings planning, coding, verification, security review, and release together through named specialists. Get a working change, the checks behind it, and a handoff you can review.
- Build
- Named specialists
- Work
- Separate workspaces
- Coordination
- Local by default
Why ATOM
From a clear brief to a usable result.
ATOM keeps planning, implementation, review, and release connected. You get software you can try and a record you can use to decide what is ready for the next step.
02
Protect work already in progress
Implementation happens in a separate, traceable workspace before any approved integration.
03
See the whole handoff
The final report shows what passed, what failed, what was skipped, and what still needs attention.
ATOM integrations
One workflow across AI coding tools.
Explore the ATOM integrations for Codex, Claude Code, and Code Puppy. Each brings named specialists, bounded permissions, and recorded results to its host. Release availability varies by integration.
Original edition
Codex
Named specialists, isolated workspaces, build history, and inspectable receipts inside Codex.
Public downloads are paused while account-linked delivery and the installable product are being prepared.
Real application built
Claude Code
ATOM's native Claude workflow produced LicenseGate, a working local application with a recorded five-stage build.
The native workflow uses Claude specialists. Optional Codex cross-checking is a separate integration.
Live build completed
Code Puppy
A separate ATOM package installs and loads through the public Code Puppy host without another ATOM edition or the source checkout.
All five stages completed a live build: 49 tests passed and 15 receipts authenticated. Customer distribution remains in preparation.
Five named responsibilities
Clear ownership at every step.
Each role has a defined responsibility, and ATOM records who did what. When roles share the same provider or runtime, ATOM says so instead of calling the review independent.
- 01
Architect
Set the brief
Clarifies the goal, the limits, and how success will be checked.
- 02
Builder
Build in a separate workspace
Implements the agreed work without writing over your active tree.
- 03
Verifier
Check the actual change
Reviews the change and the recorded checks, including anything that failed or could not be verified.
- 04
Security
Review security-sensitive changes
Reviews changes that affect security, identity, sensitive data, or code execution.
- 05
Release
Prepare the handoff
Summarizes readiness and open issues. The final assessment stays tied to the recorded results.
Built for accountable work
You stay in control.
ATOM coordinates the work; it does not grant itself permission. You approve consequential actions, and the final report only claims what the record supports.
Example final assessments
Ready within checked scope
READY_WITHIN_PROOF_BOUNDARYPartially verified
PARTIALLY_VERIFIEDNot ready
NOT_READYBlocked
BLOCKEDCancelled
CANCELLEDYou approve the scope
Specialists work within the task and permissions you set.
Observed results come first
Repository and runtime results carry more weight than a model's account of what happened.
Open issues stay visible
Failed checks, open questions, and interruptions stay in the handoff.
Local by default
Workspaces and build records stay local. Model requests use your configured provider; local coordination does not mean offline AI. Licensing is kept separate from your source code and prompts.
Recorded September 26–27, 2026
Working software is the point.
LicenseGate is a concrete result of ATOM coordinating a build in Claude Code. Code Puppy extends that workflow to another host. These results describe specific builds and checks, so you can see exactly what has been exercised.
Real application build
LicenseGate in Claude Code
- A local app for scanning dependency licenses and generating NOTICE files.
- All five specialist stages completed; 82 application tests passed.
- The Windows launcher opened, scanned a real project, generated a notice, and exited cleanly.
- 15 authenticated receipts recorded the build. Same-provider review; network access was not blocked during validation.
The published evidence includes source commits, a fresh 82-test run, and a summary of the verified build receipts. Private receipt payloads are not published.
Live build verified
Standalone Code Puppy edition
- Installed outside the development checkout and loaded by public Code Puppy 0.0.877.
- All five native specialist stages completed a live model build on September 27, 2026.
- The fixed workload passed 49 of 49 tests; all 15 receipt signatures verified.
- Code Puppy's own session retrieved the completed build. The original workload repository remained unchanged.
- Same-provider review; network access was not blocked during validation. Customer distribution remains in preparation.
Who ATOM is for
For people responsible for what ships.
ATOM is for developers, consultants, and small teams that want a clearer path from a request to software they can use, review, and improve.
Professional developers
Bring planning, implementation, and review into the coding environment you use.
Consultants
Give clients a detailed account of the work performed, the checks run, and any remaining limitations.
Small software teams
Coordinate specialist sessions with named ownership for each part of the work.
What ATOM is not
ATOM does not deploy to production on its own, guarantee correctness, certify security, or host your source code.
Paid beta
Local software. $30 launch offer.
Launch offer: $30 USD per month for subscriptions started October 14, 2026 through January 11, 2027 (America/Chicago). Those subscriptions keep $30 on renewal. New subscriptions from January 12, 2027 are $100 USD per month. ATOM is designed to run locally on your computer. Projects, live activity, evidence, and reports stay local; the account service handles your subscription and device license. Model requests use your configured provider.
Account sign-in and billing are being checked. Account-linked downloads are not available through this website yet.
Please do not include source code, prompts, diffs, repository paths, credentials, account or license details, payment data, raw logs, or diagnostic files in your message.
- Demonstrated
- Working application builds
- Access
- Public signup in preparation
- Purchase
- Paid checkout not yet open
- Policies
- Pre-release drafts