The LGTM (Page 22)

The LGTM

Sign in Subscribe

MCP Structured Content Is Not Optional If the Next Tool Call Needs the ID

MCP’s split between human-readable content and machine-shaped structuredContent is useful right up until the agent cannot see the field it needs for the next tool call. OpenClaw PR #87540 fixes one of those deceptively small bridge bugs: OpenClaw exposed structuredContent to the model only when normal content[] was empty.

Broken Context Engines Should Degrade, Not Own the Process

A broken context engine should not get to own the whole process. That is the useful premise behind OpenClaw PR #87640, a fresh patch that adds process-local quarantine for failing non-legacy context engines, reports the quarantine through health surfaces, and downgrades future context-engine work to legacy instead of letting one

OpenClaw 2026.5.27 Is a Boundary-Setting Release, Not a Feature Victory Lap

OpenClaw 2026.5.27 Is a Boundary-Setting Release, Not a Feature Victory Lap

OpenClaw v2026.5.27 is not a victory lap release. It is a boundary-setting release, which is more important and much less marketable. The changelog is full of the kind of fixes that only become urgent after an agent platform has accumulated enough channels, plugins, model routes, helper processes, memories,

Copilot Studio’s Mistral Gate Is the Real Azure AI Story

Copilot Studio’s Mistral Gate Is the Real Azure AI Story

Microsoft adding Mistral Medium 3.5 to Copilot Studio sounds, at first glance, like another checkbox in the enterprise AI model buffet. Useful, sure. But the actual story is not that makers get one more model in a dropdown. The story is that Microsoft is turning Copilot Studio into a

Grok Build’s Memory and Command Surface Turns the CLI Into a Stateful Agent Runtime

Persistent memory is where coding agents stop feeling like clever terminals and start behaving like stateful runtimes. That is useful. It is also where old assumptions, stale decisions, local hacks, and occasionally secrets can acquire a longer half-life than anyone intended. xAI’s refreshed Grok Build documentation is interesting not

xAI’s Management API Gives Grok the Admin Surface Teams Actually Need

xAI’s Management API Gives Grok the Admin Surface Teams Actually Need

xAI is doing the least glamorous work in the AI platform stack, which is exactly why this update matters. The company’s refreshed Management API documentation is not a model launch, not a benchmark chart, and not another demo of Grok writing a React component. It is the admin surface

Goose 1.36 Turns Code Review, Hooks, Skills, and Goals Into the Agent Runtime

Goose 1.36.0 is not a “new buttons in the chat window” release. It is more interesting than that, which is inconvenient for anyone trying to reduce coding-agent progress to model benchmarks. The release turns several things teams have been improvising around — code review, permission hooks, reusable skills, goal

SkillGrad Treats Agent Skills Like Code That Needs an Optimizer, Not a Pep Talk

Agent skills are being treated too much like helpful markdown and not enough like dependencies. That is the mistake SkillGrad is trying to correct. A skill can change how an agent edits a spreadsheet, reads a table, calls a tool, writes code, or follows a procedure. If that artifact can