openclaw - The LGTM

The LGTM

Sign in Subscribe

openclaw

A collection of 263 posts

OpenClaw Finally Counts HTTP API Tokens Where Operators Spend Money

Agent cost dashboards have a simple failure mode: they look useful while quietly ignoring the path where the money is actually spent. OpenClaw PR #96227 fixes one of those failures. OpenAI-compatible HTTP ingress traffic was emitting model-call events, but not model.usage, the event that downstream consumers use for token

OpenClaw’s Inline-Eval Patch Is the Boring Guardrail Vibe Coding Needs

The boring parts of agent security keep doing the real work. OpenClaw PR #96216 is not glamorous: it teaches strict inline-eval detection that python3.13 -c, /usr/bin/pypy3.10 -c, PHP -B/-E/-R, and R/Rscript -e/--exec are still inline code execution. That sounds obvious. It was

OpenClaw Is Closing the Policy Gap Between Who Asked and What Tool Runs

OpenClaw Is Closing the Policy Gap Between Who Asked and What Tool Runs

Approval gates have a branding problem: they look like security controls, but too often they are just modal dialogs with incomplete context. OpenClaw PR #96211 is interesting because it goes after the field most agent platforms quietly hand-wave: requester origin. Not just “what tool is about to run,” but who

OpenClaw’s Fallback Fixes Show the Difference Between Having Backup Models and Actually Using Them

Every agent platform eventually discovers that “we configured fallback models” is not the same as “fallback will happen under the failure we actually hit.” OpenClaw’s June 23 reliability PRs are a tidy case study in that gap. PR #96096 caps cron cloud-model stream idleness at 60 seconds. PR #96097

OpenClaw’s OPENCLAW_SESSION_ID PR Turns Bash Commands Into Auditable Agent Work

OpenClaw’s OPENCLAW_SESSION_ID PR Turns Bash Commands Into Auditable Agent Work

A single environment variable is not usually a headline. In an agent runtime, it can be the difference between “some shell process did something” and “session X, acting on request Y, spawned this command at this time.” OpenClaw PR #96104 adds OPENCLAW_SESSION_ID to bash tool subprocess environments, and

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

OpenClaw’s Approval Flow Has a Routing Bug, Which Is Exactly Why Approval Gates Need End-to-End Semantics

OpenClaw’s Approval Flow Has a Routing Bug, Which Is Exactly Why Approval Gates Need End-to-End Semantics

Approval gates are supposed to be the part of an agent platform where everyone can finally relax. The model wants to run something risky, the runtime pauses, the human approves or denies, and the system continues under supervision. OpenClaw issue #96103 is a useful reminder that this picture is too

Task Guard’s NO_REPLY Bug Shows Why Agent Safety Instructions Need Exit Conditions

Task Guard’s NO_REPLY Bug Shows Why Agent Safety Instructions Need Exit Conditions

The uncomfortable thing about prompt-based safety is that the model keeps reading the prompt after the moment you meant it to apply. OpenClaw issue #95773 is a clean example: Task Guard tells the model that the final reply for the turn “must be and can only be NO_REPLY,” then

OpenClaw’s Model-Call Telemetry PR Makes Prompt Cost Debuggable at the Span Where It Happens

OpenClaw’s Model-Call Telemetry PR Makes Prompt Cost Debuggable at the Span Where It Happens

Every agent cost investigation eventually starts with the same miserable question: which part of the prompt got expensive? The invoice says tokens. The trace says a model call happened. The runtime says the agent was “working.” None of that tells you whether the bill came from duplicated system instructions, a

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