openclaw - The LGTM (Page 4)

The LGTM

Sign in Subscribe

openclaw

A collection of 263 posts

Qwen Code Is Turning Agent Loops Into Scheduled Infrastructure

Qwen Code Is Turning Agent Loops Into Scheduled Infrastructure

The interesting part of Qwen Code this week is not that Alibaba’s coding agent learned another trick. It is that the project is starting to treat agent autonomy like infrastructure: persisted schedules, overload contracts, ownership election, and configuration approvals that survive contact with restarts and multiple clients. That sounds

OpenClaw Subagents Reporting “Cancelled” While Still Running Is a Control-Plane Truthfulness Bug

OpenClaw Subagents Reporting “Cancelled” While Still Running Is a Control-Plane Truthfulness Bug

Multi-agent systems do not need cheerful status. They need truthful status. If work is waiting, say waiting. If it failed, say failed. If it was cancelled, reserve that word for actual cancellation. The moment an orchestration platform tells a user “Background task cancelled” while the subagent keeps running and eventually

OpenClaw’s `message_sending` Hook Bypass Is the Kind of Security Bug That Makes Extensions Look Safer Than They Are

OpenClaw’s `message_sending` Hook Bypass Is the Kind of Security Bug That Makes Extensions Look Safer Than They Are

A security hook that silently does not run is worse than no hook. No hook forces operators to be honest about the risk. A documented hook that appears installed, loaded, and available — while major delivery paths skip it — creates the kind of false confidence that gets secrets posted to channels

OpenClaw v2026.6.x Prompt Bloat Shows Why Agent Platforms Need Context Budgets, Not Just Bigger Models

OpenClaw v2026.6.x Prompt Bloat Shows Why Agent Platforms Need Context Budgets, Not Just Bigger Models

OpenClaw’s prompt-bloat report is a reminder that context windows are not RAM. You do not get to pour every tool description, channel hint, safety rule, UI affordance, and delegation policy into the front of a model run and call it “free” because the model advertises 128K tokens. The bill

OpenClaw’s WhatsApp ACP Binding Bug Is a Sandbox Boundary Problem, Not a Routing Inconvenience

The dangerous OpenClaw bug this morning is not that WhatsApp routing is awkward. Awkward routing is a support ticket. The reported failure in issue #92449 is sharper: a WhatsApp direct message can resolve to the intended agent ID while failing to materialize the configured ACP runtime, which means a conversation

OpenClaw’s Default-Model Doctor PR Is the Gemini Migration Story in Miniature

The ugliest AI-tooling failure is not “the model is unavailable.” It is “the tool says this dead model is your default, then tells you the model does not exist, then fails your agent run anyway.” That is not an error message. That is a trust withdrawal. OpenClaw PR #92292 addresses

OpenClaw’s CoreWeave Provider PR Turns Open-Model Inference Into a First-Class Agent Runtime Choice

Provider support usually looks like plumbing until the first time an agent run dies because the model name was right, the base URL was wrong, the context window metadata was missing, and nobody remembered which custom header the hosted inference service wanted. OpenClaw PR #92243 is interesting because it takes