Skip to Content
IDEsDevinCloud ACUs

Devin Cloud ACUs

Devin Cloud bills in ACUs (Agent Compute Units) — not just tokens. A session includes planning, context gathering, code execution, browser actions, and tool use, plus a slice of VM time.

Hub: Tokenminning in Devin.

What ACUs include

ComponentNotes
LLM inferenceTokens on planning and edits
ActionsShell, browser, tool execution
VM timeUsually small fraction of total
Windows sessions~9% ACU premium vs Linux

Cloud Devin sleeps when idle. No usage while sleeping, waiting for your reply, or while tests run. See Usage .

Measure cloud spend

ToolUse
Session InsightsPer-session ACU/credit consumption
Settings → Plans (self-serve)Quota remaining
Settings → Consumption (enterprise)Org rollups
Session metrics API Category breakdown

Desktop metering: Token usage.

Scope tasks to cut ACUs

PatternACU impact
Vague “build me an app”Long exploration loops
One message, no acceptance criteriaBack-and-forth clarification
Local-sized fix in cloudVM overhead for laptop work — use Devin Local
Open-ended “stand by” threadKeeps session context hot

First message checklist:

  • Defined end goal
  • Acceptance criteria
  • Files or areas in scope
  • Milestones for large work (split across sessions)

vs Devin Desktop

WorkloadPrefer
IDE pair programmingDevin Local / Adaptive
Autonomous multi-hour projectCloud with phased sessions
Quick grep-level fixDesktop — not cloud VM

Guardrails

  • Let idle sessions sleep
  • Split big projects across sessions with review gates
  • Enterprise: org ACU limits via usage configuration API 
Last updated on