Skip to content
AtomicReps
Docs
Home

How Atomic Reps works

These pages cover the question in your coding agent and your editor, the Slack integration, the web daily rep and the emailed question of the day, and what data moves in and out of each.

In a coding agent, Atomic Reps asks short questions on the topics the agent just worked on, after the task is finished. The agent quickstart connects your agent in two commands, and the full reference covers the VS Code extension, the command line tool and the iPhone app.

In Slack, Atomic Reps delivers one engineering question a day into a Slack channel your team already uses. A member answers with a single click; the verdict and the explanation come back only to them, as an ephemeral message no one else in the channel can see. At the end of the day the question closes and we post nothing else: no count, no accuracy, no ranking.

We do not read your messages. Atomic Reps requests no message-history scope, ingests no source code, and never trains AI on your data (see the Security page and data flows for the authoritative statements). The only input we process is the answer you submit through our interactive components. The pages below document every command, the lifecycle of a rep, the payload of each Slack event, the OAuth scopes we request, and how long we keep each category of data.

Slack is not required. The same daily question runs on the web at /daily, and we can email it to you on a cadence you pick. The daily rep page covers both loops; data flows documents what is inside an email answer link and how unsubscribe works.