AO Wrapped
AO Wrapped reads the Agent Orchestrator telemetry already sitting on your disk and prints what your agents actually did. Every merge is joined to the session that produced it, which is the one thing a screenshot cannot fake.
“Thrilled to share that I’ve been leveraging AI to 10x my velocity. The future of engineering is here 🚀”
the flex was never the post
Your agents needed you 14 times this week. That's not a flex. That's the point.
npx ao-wrapped --publish --api https://ao-wrapped.vercel.appDrop --publish and it never touches the network. Add --dry-run and it prints the exact JSON instead of sending it.
Read-only, on your machine
~/.ao/data/ao.db — sessions, pull requests, CI checks and the change log. Opened read-only, always. Nothing is written back.
No diffs. No prompts.
Repo names, branch names, PR titles, file paths, commit messages and diffs are not read into the payload at all. There is no field they could travel in.
Counters and closed enums
Every field is a number, a date, or one of a fixed set of words. Run --dry-run to print the exact JSON before anything leaves.
Merges earn points and every interruption subtracts them, so a workforce that shipped less while asking you nothing beats one that shipped more and needed a babysitter.
| Outcome | Why | Points |
|---|---|---|
| Merge after a conflict | hardest loop to close alone | +20 |
| Merge after CI went red | the exact loop AO exists for | +18 |
| Merge after a review round | read the feedback, acted on it | +16 |
| Clean merge, first pass | the baseline unit | +10 |
| PR opened, never merged | work happened and can be read | +3 |
| Session died, no PR | no penalty for trying | 0 |
| You had to step in | charged to that session only | −4 |
1 session died in the week above. No points deducted — we're not monsters.
an agent turning its own red build green, +18
2026-W33 · resets Monday · Mon, Aug 10 — Sun, Aug 16
| # | Builder | Merges | Tasks | Nudges |
|---|---|---|---|---|
| 1 | dewansh-shukla | 26 | 11 | 14 |
