On this page

Treat ACU as work, not minutes

An autonomous agent can spend time browsing code, running commands, recovering from errors, and revising a solution. ACU consumption reflects more than elapsed wall-clock time, and contract pricing can vary.

Do not hardcode a universal dollar value unless it matches your account. Use the plan or contract view as the billing source.

Track by session and outcome

For each Devin session, record the task type, ACUs consumed, duration, and whether the result was merged, accepted with edits, or abandoned. That makes it possible to compare agent effort with delivered value.

A failed run is still useful data. Repeatedly expensive failures often point to unclear acceptance criteria, missing repository context, or a task that should be decomposed.

Keep your usage visible while you work. Get Super Notchy for $27 ↗

Use account limits as guardrails

Enterprise controls can set account-level local agent ACU limits. Even without that control, monitor daily and weekly plan usage and alert before the remaining pool becomes too small for planned work.

Super Notchy includes Devin among its supported account views where the local session exposes the needed reading. Use the persistent indicator for awareness and Devin's own account tools for authoritative billing detail.

Sources and further reading