agent-state-machine - The LGTM

The LGTM

Sign in Subscribe

agent-state-machine

A collection of 8 posts

Claude Code’s Remote Auto-Compaction Bug Turns Context Management Into Hidden Runtime State

Claude Code’s Remote Auto-Compaction Bug Turns Context Management Into Hidden Runtime State

Context compaction is the garbage collector for coding-agent state. Nobody wants to think about it until it silently stops running. That is why Claude Code issue #70477 is more interesting than a routine token-cost complaint. The report says remote or bridge-attached Claude Code sessions can skip threshold auto-compaction and ignore

Subagents That Finish Silently Are a Product Bug, Not a UX Quirk

Subagents That Finish Silently Are a Product Bug, Not a UX Quirk

The most damaging bug in a multi-agent system is not always the one where the worker fails. Sometimes the worker finishes, the parent synthesizes the answer, the transcript contains the output, and the human still gets nothing. That is the failure mode in OpenClaw issue #96105, and it is exactly

Microsoft Agent Framework’s ‘Claw’ Series Turns Agent Architecture Into Reviewable Infrastructure

Microsoft Agent Framework’s ‘Claw’ Series Turns Agent Architecture Into Reviewable Infrastructure

Microsoft’s latest Agent Framework tutorial is framed like a friendly “build your own claw” walkthrough. The branding is whimsical; the engineering problem is not. What Microsoft is really publishing is a reference shape for the thing most agent demos quietly hand-wave: the harness that keeps a model loop from

ACP Background Tasks Need to Wake the Parent Agent, Not Just Announce That They Finished

ACP Background Tasks Need to Wake the Parent Agent, Not Just Announce That They Finished

Background tasks are supposed to buy back attention. If an agent can delegate work to an ACP harness, wait for completion, and then leave the parent conversation sitting there like a CI job with no status check, the platform has not built orchestration. It has built a very expensive notification

xAI’s Deferred Chat Completions Add the Missing Middle Between Wait on the Request and Batch It Overnight

xAI’s Deferred Chat Completions Add the Missing Middle Between Wait on the Request and Batch It Overnight

xAI’s Deferred Chat Completions are the kind of API feature that looks minor until you have to build around the absence of it. Most AI platform diagrams pretend model calls come in two shapes: synchronous requests where the user waits, and batch jobs where nobody cares until tomorrow. Production