mlsanityData to 14 Oct 2026

Tokenomics: Quantifying Where Tokens Are Used in Agentic Software Engineering

arXiv 2601.14470 ↗First posted 20 Jan 2026cs.SE cs.AI cs.MAcited by 12

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

LLM-based Multi-Agent (LLM-MA) systems are increasingly applied to automate complex software engineering tasks such as requirements engineering, code generation, and testing. However, their operational efficiency and resource consumption remain poorly understood, hindering practical adoption due to unpredictable costs and environmental impact. To address this, we conduct an analysis of token consumption patterns in an LLM-MA system within the Software Development Life Cycle (SDLC), aiming to understand where tokens are consumed across distinct software engineering activities. We analyze execution traces from 30 software development tasks performed by the ChatDev framework using a GPT-5 reasoning model, mapping its internal phases to distinct development stages (Design, Coding, Code Completion, Code Review, Testing, and Documentation) to create a standardized evaluation framework. We then quantify and compare token distribution (input, output, reasoning) across these stages. Our preliminary findings show that the iterative Code Review stage accounts for the majority of token consumption for an average of 59.4% of tokens. Furthermore, we observe that input tokens consistently constitute the largest share of consumption for an average of 53.9%, providing empirical evidence for potentially significant inefficiencies in agentic collaboration. Our results suggest that the primary cost of agentic software engineering lies not in initial code generation but in automated refinement and verification. Our novel methodology can help practitioners predict expenses and optimize workflows, and it directs future research toward developing more token-efficient agent collaboration protocols.

Key facts. Cited by 12 papers in the map (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 6 of its 21 references that are in the map. First posted on arXiv 20 Jan 2026.

Builds on

6 of 21 references.

Closest ancestors · 1

Same direction, newest first

  1. 2023ChatDev: Communicative Agents for Software Development16 Jul

Other references · 5

  1. 2023A Survey on Large Language Model based Autonomous Agentscited by 2,242
  2. 2023Encouraging Divergent Thinking in Large Language Models through Multi-Agent Debatecited by 1,011
  3. 2025Exploring Autonomous Agents: A Closer Look at Why They Fail When Completing Taskscited by 20
  4. 2025Rethinking Autonomy: Preventing Failures in AI-Driven Software Engineeringcited by 4
  5. 2025Co-Saving: Resource Aware Multi-Agent Collaboration for Software Developmentcited by 3

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2026: 12.

12 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2026LLM-Based Agentic Systems for Software Engineering: Challenges and Opportunities
  2. 2025Designing LLM-based Multi-Agent Systems for Software Engineering Tasks: Quality Attributes, Design Patterns and Rationale
  3. 2026Taming Scylla: Understanding the multi-headed agentic daemon of the coding seas
  4. 2026Code Health in LLM-Based Test Generation: Effectiveness and Token Efficiency
  5. 2025LoCoBench-Agent: An Interactive Benchmark for LLM Agents in Long-Context Software Engineering
  6. 2026TraceLab: Characterizing Coding Agent Workloads for LLM Serving
  7. 2025Understanding Software Engineering Agents: A Study of Thought-Action-Result Trajectories
  8. 2026Evaluating LLM Agents on Automated Software Analysis Tasks