OC Agent Stops Mid-Task and Demands Permissions — Users Report Regressive Behavior in v2026.5.22

A user on r/openclaw reports that the OC agent (version 2026.5.22) frequently stops working mid-task, fails to send final updates, and has recently started asking for permission before carrying out every action — a regression from previously autonomous behavior.
Symptoms
- Agent shows "typing" in Telegram and sends initial status messages like "I'm starting work," then does nothing further. The task never completes.
- If the user sends a
?a few minutes later, the agent resumes and apologizes for the error. - The agent sometimes "forgets" to send a final update upon task completion.
- The agent now asks for permission before every subtask, whereas before it handled certain actions autonomously.
Example
Command: Investigate why the CPU load is spiking sporadically.
Previous response (weeks ago):
"I've checked it. Tasks X, Y, and Z are the culprits. I've installed a small tracker so we can pinpoint exactly when it happens. I'll get back to you in 24 hours with the results."
Current response:
"I've identified tasks X, Y, and Z as the cause of the CPU load. Recommendation: I could build a small tracker to monitor the system for 24 hours."
User's Attempted Fix
The user asked the OC agent to fix the issue itself. The agent only modified .md files and "tightened its rules" — which did not help.
Key Takeaway
This appears to be a behavioral regression introduced in recent updates (user is on v2026.5.22). The agent becomes overly cautious, halts mid-task, and demands confirmations. A temporary workaround is to send ? to resume, but the underlying issue needs patching.
📖 Read the full source: r/openclaw
👀 See Also

Dangerously Skip Reading Code: When LLMs Write Code Faster Than You Can Read It
What if we stop reviewing LLM-generated code and instead treat it like machine code? Move rigor to specifications and tests.

Analysis of 2,181 Remote MCP Server Endpoints Shows Reliability Issues
An automated health check of 2,181 remote MCP server endpoints found that only 9% are confirmed up and healthy, with 52% completely dead and 37% requiring authentication. The data includes category breakdowns, latency measurements, and uptime statistics.

Claude Platform on AWS Now GA: Native Anthropic Experience via IAM, CloudTrail, and AWS Billing
AWS announced GA of Claude Platform on AWS, giving developers direct access to Anthropic's native Claude experience through existing AWS accounts with IAM auth, AWS billing, and CloudTrail logging — but customer data is processed outside AWS security boundary.

Claude Code Opus Fails with Rate Limit Error Despite Available Weekly Capacity
A Claude Max subscriber reports that Claude Code Opus returns 'API Error: Rate limit reached' even though their usage dashboard shows 97% of their weekly 'All models' capacity remains unused. The issue occurs specifically in Claude Code while Opus works normally on claude.ai from the same account.