OpenClaw 2026.8.2 Regression: Agent Won't Post Tokens, Prefers Native X Search Over Custom Skills

A developer running OpenClaw 2026.8.2 reports that the recent release broke two parts of an established workflow, and they're downgrading for the first time since starting with the harness in February/March 2026. The post, from u/OleCuvee, is framed as a concrete regression report rather than a general complaint.

Refusing to relay one-off credentials

The first change is behavioral. After upgrading, the agent now enforces a strict rule in Telegram sessions: it will not post secrets, passwords, or tokens. The user's setup relies on short-lived credentials — one-off tokens and passwords they throw away — being delivered through the Telegram session. That workflow has been in place for roughly nine months. The new guardrail adds a manual step: open Termux on mobile, SSH to a remote system, and read a text file the agent writes credentials into. From the user's perspective, the risk decision should belong to the owner of the installed platform, not to OpenClaw maintainers. They explicitly reject the suggestion to fork OpenClaw and rebase it on every release.

Custom X skills bypassed in favor of the native tool

The second regression is about tool selection. Months ago the user built a skill that wraps their own x-search API tools for working with tweets on X. After upgrading to 2026.8.2, the agent reported it could not verify "last hour huge traction" because the native X search tool is installed but not exposed by the gateway right now. The agent chose to depend on the native X search tool instead of the custom skill/tools it had been using. The user's objection is straightforward: if the custom tools are available, why prefer the native path that is currently unexposed?

Downgrading instead of forking

The author notes they have never complained about broken upgrades before and understand how to operate fragile systems. The issue is the direction itself — OpenClaw taking away decision-making power over what the agent can do per channel and which skills or tools it should prefer. They mention writing a simple in/out webhook wrapper for a Telegram bot as an hour-long job, and float the possibility of moving back to opencode. They are not calling it the end of their OpenClaw journey, but say the little claw monster is heading in a direction that no longer serves their workflows. They also explicitly rule out switching to alternatives they dislike.

Practical takeaway for anyone on 2026.8.2 with similar custom skills: the release appears to change both credential-handling behavior and tool preference order. If your workflow depends on the agent relaying disposable tokens through a chat channel, or on a custom skill taking precedence over a native tool, verify behavior before upgrading.