Session analytics and the two loops
Two numbers per project: how long your coding agent took to open a pull request, and how long the pull request took to merge.
The two loops
| Loop | Measures | Comes from |
|---|---|---|
| Agentic loop | First prompt → pull request opened | The block below: its step minutes, added up. |
| CI/CD loop | Push → merge | GitHub: from when the pull request opens to when it merges. No block needed. |
The app shows each loop’s median over pull requests opened in the last 7 days, on Home and on each project.
The block
Your coding agent adds this to the description of each pull request it opens, and updates it when it pushes again:
<details><summary>🛸 IonWarp Session Analytics</summary>
<!-- ionwarp:session-analytics v3 -->
```yaml
harness: Claude Code (Opus 5)
session_flow:
- step: plan
detail: read the prior plan docs; scoped the fix to one shared seam
min: 5
- step: implement
detail: one primitive replaced three divergent per-page copies
min: 30
- step: verify
detail: scoped vitest + a Playwright spec against the preview worker
min: 10
dev_testing:
- tool: vitest
duration_min: 4
cheatcodes:
- "prompt:one-primitive — named the shared seam before touching any page"
biggest_iteration_speed_improvement: faster scoped preview builds
```
</details>IonWarp reads it when the pull request opens and whenever the description is edited. The block is optional and never gates CI.
Fields
| Field | What to put |
|---|---|
harness | The coding agent and its model, like Claude Code (Opus 5). |
session_flow | Each step in order: step, a short detail and its minutes as min. Up to 8 steps; their minutes are the agentic loop. |
dev_testing | Each test tool run: tool and duration_min. |
cheatcodes | Prompts or tricks that saved time, one per line, up to 8. |
biggest_iteration_speed_improvement | What would have made the loop faster. |
Text values are cut at 240 characters. The review comment’s 🧭 Review log names what wrote the pull request:
🤖 written in Claude Code (Opus 5) — plan 5m · implement 30m · verify 10mAsk your coding agent
Put this in your AGENTS.md or CLAUDE.md:
## IonWarp session analytics
On every pull request you open, add the IonWarp session analytics block to the
description, and update it when you push again. Format and fields:
https://ionwarp.com/docs/session-analyticsWhen the format drifts
Agents type the block from instructions, so IonWarp reads it loosely. Without the <!-- ionwarp:session-analytics v3 --> marker, a <details> whose summary names IonWarp, or a heading that says IonWarp Session Analytics, works when a ```yaml fence follows. Older lines such as planning_min: 3 still count. A block IonWarp can’t read is ignored, never an error.