agentic-ai-token-usage - The LGTM

The LGTM

Sign in Subscribe

agentic-ai-token-usage

A collection of 13 posts

MCP’s write_file Escaping Problem Is Really a Tool-Call Serialization Tax

MCP’s write_file Escaping Problem Is Really a Tool-Call Serialization Tax

Base64 is ugly. Retry loops caused by broken JSON tool calls are uglier. A fresh issue in the Model Context Protocol servers repository proposes adding an optional content_base64 parameter to write_file, plus a matching newText_base64 path for edit operations. The request is narrow: let agents send file

Claude Code 2.1.185 Turns a Retry Message Into a Production-Signal Problem

Claude Code 2.1.185 Turns a Retry Message Into a Production-Signal Problem

Sometimes the smallest changelog item is the one that tells you where the product is hurting. Claude Code 2.1.185 shipped with one public note: the stream-stall message now says “Waiting for API response · will retry in …” instead of “No response from API · Retrying in …”, and the hint appears

Qwen Code v0.18.4 Turns Local Agents Into Runtime Infrastructure

Qwen Code v0.18.4 Turns Local Agents Into Runtime Infrastructure

Qwen Code v0.18.4 is easy to undersell if you read it as a grab bag of CLI features. Extensions, token accounting, workflow budgets, wakeups, daemon health, QQ Bot support, loop detection — none of those sound like a single launch narrative. That is exactly why the release matters. Alibaba’

Copilot Finally Exposes Per-User AI Credit Burn. Now Teams Can Stop Guessing Which Agent Workflows Are Expensive

Copilot Finally Exposes Per-User AI Credit Burn. Now Teams Can Stop Guessing Which Agent Workflows Are Expensive

Copilot’s credit meter has finally moved from accounting fog to something engineering teams can actually inspect. GitHub added ai_credits_used to the Copilot usage metrics API, giving enterprise administrators and organization owners a per-user view of AI credit consumption across one-day and 28-day user reports. That sounds like

Qwen Code’s June 19 Patch Stack Is About Operability, Not Benchmarks

Qwen Code’s June 19 patch stack is the sort of release work that rarely gets a launch thread and absolutely determines whether developers trust an agent after lunch. No new frontier model. No benchmark victory lap. Instead: memory retention, token telemetry, ACP child-process hygiene, Windows sandbox parsing, and a

Microsoft Foundry Is Pitching OpenEnv as the Enterprise Agent Training Loop, Not Another Chatbot Stack

Microsoft Foundry Is Pitching OpenEnv as the Enterprise Agent Training Loop, Not Another Chatbot Stack

Microsoft’s latest Foundry post is not selling another chatbot. Good. The industry has enough demo loops that answer once, forget everything, and then get celebrated as “agentic” because they called a tool. The more interesting claim is that enterprise AI systems need gyms: controlled environments where agents can practice

Stagehand 3.6.0 Turns WebMCP, Action Caching, and Verifiers Into Browser-Agent Runtime Primitives

Stagehand 3.6.0 Turns WebMCP, Action Caching, and Verifiers Into Browser-Agent Runtime Primitives

Browser agents are past the “can it click the button?” phase. The harder question is whether the runtime can expose page-native tools safely, avoid paying an LLM for the same action twice, and produce enough evidence to debug failure without archaeology. Stagehand 3.6.0, published by Browserbase on June