The LGTM (Page 11)

The LGTM

Sign in Subscribe

Microsoft Foundry’s APIM Pattern Makes the AI Gateway Boring Enough for Production

Microsoft Foundry’s APIM Pattern Makes the AI Gateway Boring Enough for Production

Enterprise AI architecture keeps rediscovering an old truth: the hard part is not calling the model. The hard part is calling the right model, from the wrong region, under the right identity, without punching a hole through your network model or your compliance story. Microsoft’s new guidance on cross-region

Codex Starts Giving Context Windows Provenance, Not Just Token Counts

Codex Starts Giving Context Windows Provenance, Not Just Token Counts

Token counters are table stakes now. The more interesting question is whether a coding agent can explain how it arrived at the context it is using after compaction, rollback, resume, and a few long-running tool sessions have rearranged the furniture. That is the useful read on OpenAI’s latest Codex

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