coding-agent-budget-controls - The LGTM (Page 2)

The LGTM

Sign in Subscribe

coding-agent-budget-controls

A collection of 23 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 Routines Need Output-Branch Contracts, Not Prompted Git Etiquette

Claude Code Routines Need Output-Branch Contracts, Not Prompted Git Etiquette

Scheduled coding agents are not chat sessions with alarms. They are job runners. Job runners need output contracts. That is the uncomfortable lesson in a fresh Claude Code issue reporting that scheduled cloud Routines can finish work on a harness-assigned branch such as claude/stoic-fermi-azzeU instead of the canonical branch

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

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

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