Skip to content

What tools measure how engineers work with AI coding agents?

Short answer

Three kinds of tool cover this ground. AI platforms report usage, tokens and cost. Delivery analytics report commits, pull requests and deployment metrics. A third kind, which Ascenda builds, measures the human side: how engineers steer agents, how often they're interrupted, how much they redo, and how they say the work felt.

Why it matters

Usage and delivery numbers can both rise while the work gets harder to sustain. An organisation adopting AI agents needs to see the human side as well: how much supervision the agents need, and who carries it.

How Ascenda helps

Engineers install Flow, a macOS app that reads the AI tools they already use: Claude Code, Codex CLI, Cursor and Gemini CLI. From that, Ascenda reports to the organisation:

  • Exposure and work composition: creating, verifying and supervising share, concurrency, oversight load and after-hours use.
  • Friction: interventions, failed tool calls, compactions and retry storms per active hour.
  • Self-reported state: the share of check-ins in each quadrant, as a direction against the cohort's own baseline, never a score.

Everything reaches the organisation as aggregates of at least ten people, with no individual view. Each engineer consents separately and can withdraw.

There are two engagements. The 30-day Report works from imported history, with no integration. The 90-day Study runs live.

What else you'd need

Ascenda measures the human × agent side. Delivery figures such as deployment frequency and change failure rate come from your own delivery tooling, and can sit beside the readout.

Next step

Start with a 30-day Report

The Report works from your engineers' imported history for a cohort of ten or more, with no integration, and ends in a written deliverable. The 90-day Study is the next stage and runs live.