Requesty
Data/Agentic workloads

Session depth by coding agent, April 2026

Session depth by coding agent, April 2026

Median API calls per trace_id. Only agents with trace coverage are shown.

Requesty
Claude Code has the deepest sessions at 16 median calls per trace. P95 reaches 209 calls, reflecting complex multi-step coding workflows.

How many API calls does a single coding session make? In April 2026, Claude Code has the deepest sessions at 16 median calls per trace and reaches 209 calls at P95, reflecting complex multi-step coding workflows. Roo Code sessions are shallower at 11 median calls but more numerous (6,247 traces vs 594 for Claude Code).

Why it mattersSession depth is a proxy for agentic autonomy. Deeper sessions mean the agent is performing more steps before returning control to the developer. Claude Code P95 of 209 calls per session means the top 5% of coding tasks involve 200+ round trips to the model. This drives both cost and latency accumulation.

Period
Apr 2026
Updated
May 16, 2026
ID
coding-agent-session-depth-apr26
§ 01

Key findings

  • 01Claude Code: 16 median calls, but P95 of 209 calls. The longest tail of any agent.
  • 02Roo Code: 11 median calls, consistent across months. The most predictable session depth.
  • 03Only 3 agents send trace_id consistently. Cline, OpenCode, and Zed do not populate traces.
§ 02

Data

AgentMedian callsP95 callsMax callsTotal traces
Claude Code162093.2k594
Roo Code11741.8k6.2k
§ 03

Cite as

APA
Click to copy
BibTeX
Click to copy
ID: coding-agent-session-depth-apr26·Updated May 16, 2026·Period Apr 2026