Auto
1. Frequent Breaking Changes & Update Instability
OpenClaw users consistently report that new releases often break core functionality, forcing them to revert to older versions. For example, on the OpenClaw Discord “Friends of the Crustacean” forum one user asked “OpenClaw still broken?” and noted “Many version[s] seem to have been broken ever since… basically being unusable” (www.answeroverflow.com). Similarly, another user bluntly titled their post “OpenClaw has become unusable since 2026.4.14 updates” (www.answeroverflow.com), describing persistent errors after each update. These complaints appear in many threads across Reddit, Discord, and other communities (one user even wrote “OPENCLAW Currently Sucks!!!” out of frustration (www.skool.com)). Frequency: Discussion of breaking changes is ubiquitous in OpenClaw forums. Engagement: Such posts often attract dozens of replies (e.g. 21 replies in the “unusable” thread (www.answeroverflow.com)). Severity: Very high – updates can render the agent non-functional. Recency: Ongoing – even the latest versions (as of mid-2026) are subject to complaints. Workarounds: Users often downgrade to a known-stable release. For example, after an especially bad update one user “downgraded to 2026.2.25, which is better” (www.skool.com). Developers appear aware (many fixes land quickly), but the rapid release cadence (sometimes 2–3 releases per week) makes it hard to keep up.
2. Agent Unresponsiveness and Task Failures
Many users complain that OpenClaw stops doing work unless prodded, even when it ostensibly accepts a task. One user reported that after asking OpenClaw to build a web app, “it just sat there for 2 hours doing nothing…I still need to give it a nudge to do anything” (www.answeroverflow.com). Another recounted the assistant “says things are done but are really not” and often “ignores some of my questions” (www.answeroverflow.com). In a high-profile thread, a user noted that OpenClaw would print a short confirmation but never execute a git command – “I have to poke it every few mins to do the next step” (www.answeroverflow.com). Likewise, a recent post observed that OpenClaw would “give very short responses saying he did what I asked but…actually doesn’t do anything.” (www.answeroverflow.com). Frequency: Common. Almost every bug-complaint thread includes reports of tasks stalling. Engagement: High – e.g. the “doesn’t take actions anymore” thread drew 61 replies (www.answeroverflow.com). Severity: High – this prevents OpenClaw from accomplishing tasks autonomously. Recency: Active – several recent threads (past few weeks) describe it. Workarounds: Few. Some users try rephrasing prompts or restarting the gateway, but there’s no guaranteed fix. One user suggested explicitly instructing the agent or adding reminders, but most workarounds involve restarting or reinstalling. Official Response: No clear fix yet; users hope pending updates (or changing the model to a more stable one) will improve reliability.
3. Slow Performance and High Resource Usage
OpenClaw is notoriously slow compared to a chatbot, and updates have sometimes made it worse. The developers themselves warn that complex tasks can take 5–15 seconds or more per step (openclawconsult.com). However, users report much longer delays after certain updates. In one analysis of May 2026 threads, the v2026.4.29 update was said to cause “a three-minute delay in answering requests and excessive CPU usage,” prompting many to downgrade (8news.ai). (Indeed, one Reddit post noted 7 out of 10 users experienced ~3-minute responses, and the “temporary fix” was to revert to v4.23 (8news.ai).) Even routine queries can stall: a GitHub issue for 2026.3.12 warned that the “Web UI [is] extremely slow or unresponsive after upgrading” (github.com). Frequency: Very common – almost every active user reports latency issues. Engagement: High – slowdowns fuel many support requests. Severity: Medium–high – a slow agent is frustrating but sometimes tolerable. Recency: Persistent. Workarounds: Users often adjust model settings (e.g. using faster LLMs or fewer “thinking” steps) and ensure ample hardware. Some follow the openclawconsult performance guide (openclawconsult.com) to optimize (better hardware, local models, etc.). Official Response: Developers note expected slowness due to agent work, but have also shipped optimizations. Users are advised to run OpenClaw on beefier servers and use models like GPT-4o or local LLMs to reduce latency.
4. High Operating Costs for AI Models
Although OpenClaw is free to install, the real cost is API usage, which many users find expensive. Multiple posts lament the bills incurred by calling LLMs. One user reported spending $40 in one day on the Claude API after downgrading to a cheaper code plan – far more than in the previous month (www.answeroverflow.com). Another noted that even the free Ollama models require a powerful machine to use effectively. Frequency: Quite common. Many “money talk” threads on r/OpenClaw discuss bill pain. Engagement: Moderate – posts gain traction (hundreds of comments on costs). Severity: Medium – it doesn’t break OpenClaw, but it limits who can afford to run it. Recency: Ongoing. Workarounds: The main solution is to use cheaper LLMs. Users often switch to free or locked-down local models (Ollama + Llama 3, etc.) to cut costs. Written guides recommend carefully tracking and routing queries only through lower-cost models. Officially, this is expected behavior: OpenClaw’s docs stress that your own API key costs money (runmyclaw.ai).
5. Web UI and Interface Glitches
Users report various UI bugs after updates. For instance, after the v2026.3.12 update one Chinese forum user wrote that “the UI was changed a lot, but there are many problems: huge warning label in the chat window, no history or input box visible, blank areas when scrolling” (linux.do). Others complain the web interface becomes unresponsive (as noted in GitHub issues). Frequency: Fairly high; each new version seems to introduce fresh UI issues. Engagement: These complaints often appear in general discussion threads. Severity: Low–medium – interface quirks are annoying but usually can be worked around (e.g. refreshing). Recency: Recent (3.12 update, June/May 2026). Workarounds: Users reload the page or stick to an older version’s frontend. The OpenClaw team is aware – some fixes are included in patch releases (e.g., v2026.3.12 included “12+ security fixes” and UI tweaks) (www.reddit.com).
6. Installation/Environment Difficulties
Getting OpenClaw running can be tricky. On Docker/VPS setups, permission and sandbox issues often appear. One user on Hostinger VPS reported “permission and allow-list issues… spawning and memory bugs” even for basic tasks (www.skool.com). Similarly, a DigitalOcean user found that the default container lacked common tools like ls, causing OpenClaw to refuse file-listing commands (www.digitalocean.com). Frequency: Moderate – many ask for help setting up or fixing “gateway” errors. Engagement: Support forums and Q&A sites have steady posts. Severity: Medium – an installation that won’t perform tasks is effectively a blocker. Recency: Ongoing as new platforms are tried. Workarounds: Users often switch to different OS or disable Docker restrictions. Guides suggest using a clean Ubuntu VM or specialized appliances. The developers try to support major platforms, but some problems require advanced Docker configuration (e.g. adding utilities).
7. Plugin/Channel Integration Broken
The plugin/skill system is a frequent source of pain. For example, after installing or upgrading, all channel plugins often appear “disabled”. A GitHub bug report noted that after a fresh install of v2026-2-22.2, Telegram and Discord channels were listed as “plugin disabled” unless manually reinstalled (github.com). On the Discord forum, users found that adding a Telegram channel simply returned “plugin not available.” (www.answeroverflow.com). Frequency: High – nearly every support thread has plugin woes. Engagement: High – enabling messaging gateways is a core use case. Severity: High – if you can’t enable channels, OpenClaw can’t receive commands. Recency: Plenty – new plugin bugs appear with each release. Workarounds: Often, manually reinstalling the plugin helps (e.g. running openclaw plugins install @openclaw/telegram in the CLI). However, this is technical. The developers have acknowledged some plugin bugs; for instance the voice plugin issue described below was tagged a confirmed core bug in the server logic (www.answeroverflow.com).
8. Mobile App Bugs and Poor UX
In mid-2026 OpenClaw launched official iOS/Android companion apps. Early user reviews are overwhelmingly negative. As TechRadar reported, the apps launched to a 2.2-star rating on Google Play, with users calling it “unusable” and “the worst app I’ve ever used” (tech.yahoo.com). Common complaints include failed pairing and frequent crashes. Frequency: Not widely discussed (new apps), but vocal especially on the app store and tech news. Engagement: Moderate – app issues got news coverage and hundreds of comments. Severity: Medium for mobile users – the apps aren’t required, but they undermine the promise of “agents in your pocket.” Recency: Just appeared (June 2026). Workarounds: Most users still use OpenClaw via Telegram/WhatsApp instead of the buggy mobile app. The OpenClaw team has promised updates to stabilize the apps (one user noted a new 2.3 build was being tested), but many advise waiting until at least a 3.x release.
9. Security & Privacy Concerns
A more philosophical complaint is fear that OpenClaw acts like malware. Because it can run arbitrary code on your machine, security experts and users urge caution. A community summary even quoted a security pro saying OpenClaw (then MoltBot) is essentially “malware” – software running autonomously with full system permissions (www.etcetera.io). Frequency: Growing discussion, especially as the project became viral. Engagement: High on threads about privacy and architecture. Severity: Subjective – not a bug per se, but a real concern. Recency: Consistent since late 2025. Workarounds: The project itself warns less-technical users to proceed carefully. Founder Peter Steinberger has explicitly advised in Discord that if you can’t use a CLI safely, you should not run OpenClaw (discuss.erk.gg). In practice, tech-savvy users run it in isolated servers and audit any downloaded skills.
10. Removed or Missing Features
Some updates have removed features without warning. Users note that capabilities present in older versions are disabled in new ones. For example, after v2026.3.2 one user wrote that the assistant felt “locked”—“no sub-agents, no exec, just basic chat” (www.skool.com), whereas previous versions supported multiple agent personas and shell execution. Frequency: Occasional but highly visible when it happens. Engagement: Notable when discovered – often dozens of comments. Severity: Medium – loses advanced functionality but core chat still works. Recency: Has happened in recent minor releases. Workarounds: Users either stay on an older version (as above) or manually re-enable any disabled tools via openclaw onboard or configuration edits. Developers sometimes roll back such changes the next release after user outcry.
11. Hallucinations and False “Done” Responses
OpenClaw sometimes hallucinates results. Instead of performing an action, it will confidently report success. One user described it “keeps saying things are done but are really not… ignoring some of my questions” (www.answeroverflow.com). Another said it often “pretends to start a task then sits idle” unless prodded. Frequency: Fairly common for complex tasks (coding, multi-step queries). Engagement: Medium – often discussed in troubleshooting posts. Severity: Medium – it undermines trust but the session is still alive. Recency: Ongoing. Workarounds: Users have tried breaking tasks into smaller steps and explicitly checking on progress. There’s also community tooling like watchdog scripts to re-prompt the agent if it stalls. Ultimately, this is partly inherent to LLM-based agents, though developers are working on “machine discipline” safeguards.
12. Lack of Debugging Output and Logs
Many threads note that debug logs are sparse, making problems hard to diagnose. For example, a user said when OpenClaw just idles, there are “no logs, everything appears to be running fine… it’s just lazy” (www.answeroverflow.com). Administrator tools only show heartbeats and model queries, but not why an action failed. Frequency: Universal; any advanced user has noticed this. Engagement: Low – usually mentioned in comments rather than main threads. Severity: Low–medium – it means users waste time guessing fixes. Recency: Continuous. Workarounds: Power users add logging by editing the code or running in debug mode. The official CLI now has a “--verbose” flag for some commands, but many bugs occur at the agent/runtime level. (Improved logging has been requested by the community for future releases.)
13. Context Window & Memory/Compaction Issues
Some users report that context limits and memory compaction aren’t working right. In one case, after an update the assistant’s context window cap dropped from 274k tokens to 200k, and “compaction hardly ever works” (www.answeroverflow.com). This can cause OpenClaw to lose track of long-running conversations or run out of memory. Frequency: Moderate – pops up when users chain many tasks. Engagement: Lower than crashes, but noted in high-visibility threads. Severity: Medium – it can interrupt long dialogues or massive data tasks. Recency: Reported after recent updates. Workarounds: Users manually trigger openclaw tools –run compaction or split tasks. Developers have hinted that a fix is coming to restore the full 274k default window.
14. Plugin Install Commands Hangs
Several users noted that installing plugins can freeze indefinitely. A GitHub issue (#7662) documents that running openclaw plugins install /path/to/plugin simply hangs with no output (github.com), requiring a manual kill. Frequency: Less common – happens only on some systems or with some plugins. Engagement: Once reported, usually patched. Severity: Low–medium – it blocks adding new skills. Recency: Reported early 2026; closed as “stale”, so not fixed yet. Workarounds: Installing via npm or copying files manually into ~/.openclaw/extensions/ (as a user discovered in channel discussions).
15. Voice-Call Plugin Broken
OpenClaw’s built-in voice-calling feature is currently non-functional. One user tried for “two days” to make Twilio calls work. The system even reports that the plugin is “installed but… disabled due to a confirmed core bug in OpenClaw’s server initialization logic” (www.answeroverflow.com). Frequency: Not widely used (voice is new), but all voice-call threads now mention this bug. Engagement: Moderate attention on Discord/Slack user groups. Severity: Medium – voice calls are a marquee feature. Recency: Active bug (as of Feb 2026). Workarounds: None; the only solution is to wait for a fix. The developers have marked it as a known bug, and community posts suggest it will be fixed in a future update (pending proper server initialization patch).
16. Telegram Voice Notes & Other Media Failures
Users report that certain media features stop working after updates. For example, one thread asked “I updated to OpenClaw and now Telegram voice notes don’t work” (www.answeroverflow.com), and others mention broken SMS/webhook flows. Frequency: Occasional – usually tied to specific plugin versions. Engagement: Lower, as voice notes are a niche feature. Severity: Low for core use, but inconvenient. Recency: Has happened on pre-2026 upgrades. Workarounds: Rolling back the bot versions or disabling conflicting plugins. The team has been slowly fixing native voice modules; for now many users advise sticking to the latest minor release or using alternative notification channels.
17. ChatGPT/Cloud Integration Latency
OpenClaw’s OAuth integration with models like ChatGPT has introduced latency issues. A May 2026 analysis noted that requests via the OpenChat (ChatGPT) route can take 20+ seconds due to a Cloudflare blockage, severely degrading performance (8news.ai). Frequency: Specific to users who enable the ChatGPT API. Engagement: Not huge, but noted by advanced users experimenting with the model. Severity: Medium – it makes some model queries painfully slow. Recency: Recent (April-May 2026). Workarounds: Users often switch to a different endpoint (direct OpenAI API, or alternative models) or use the “Agentic codex link” (a workaround that avoids Cloudflare). The developers acknowledge the issue and are investigating alternative routing (e.g. proxying through different servers).
18. General Stability Frustration
Across forums, the overall sentiment is frustration. Many threads simply summarize users’ anger or weariness. For instance, one user’s title bluntly read “OpenClaw currently sucks!!!” (www.skool.com). Others on Reddit have asked rhetorically “OpenClaw… is it actually stable yet?” after weeks of bugfix releases. Frequency: Very high – it shows up at the top of many comment sections. Engagement: These meta-complaints often spark many replies about specific problems. Severity: It reflects user dissatisfaction, which can discourage new adopters. Recency: As long as issues persist, so does this meta-criticism. Workarounds: N/A (it’s user sentiment). In general, users advise newcomers to be prepared for a rough ride or to wait until the codebase matures further.
19. Steep Learning Curve / Risk for Novices
Finally, many users note that OpenClaw isn’t beginner-friendly. It requires command-line savvy and understanding of AI tooling. Its founder himself warned newcomers that “if you can’t understand how to run a command line, [OpenClaw] is far too dangerous for you to use safely.” (discuss.erk.gg). Novices frequently complain on Reddit that the documentation is terse and the default user interface (Telegram/chat) can be confusing. Frequency: Regular. Engagement: Less in complaints threads, more in help threads. Severity: Medium – this isn’t a bug, but it does cause many support requests. Workarounds: Communities have written “Quickstart” guides and video tutorials. Many advise new users to start with the official tutorial or a managed hosting service to avoid setup pitfalls.
20. Malicious “Skills” on ClawHub
A security hazard arose in early 2026 when researchers found hundreds of malicious community plugins (“skills”) on OpenClaw’s official registry (www.bleepingcomputer.com). These crafted skills pretend to help (e.g. “System Tools”) but actually steal secrets like SSH keys and passwords. Frequency: Low on a per-user basis, but the threat is serious. Engagement: The news prompted widespread alarms in security forums. Severity: High – it can compromise any deployment using unvetted plugins. Workarounds: Until this is addressed, users are strongly advised to only install skills from trusted sources. The OpenClaw devs and community moderators have since flagged and removed malicious entries, and recommend new users stick to core features or vetted plugins.
Community Sentiment: Overall, veteran users express frustration and fatigue. Many say OpenClaw holds great promise but is too unstable right now. The bug reports are piling up faster than fixes in some parts of the forum history. However, the project is under active development: the team rapidly pushes updates and community helpers frequently share fixes. Some categories (like UI glitches) have seen incremental improvements, while trickier issues (agent reliability, cost, malicious skills) remain contentious. In summary, the consensus is that OpenClaw still needs more polish before it lives up to its hype. Enthusiasts remain hopeful—cite by continuing cycles of bugfix releases—but the immediate past shows a growing backlog of complaints.
