Ask HN: Who is using OpenClaw?

Hacker News Discussion ↗

Hacker News readers weigh the hype around OpenClaw, an AI “agentic” automation framework that runs on your own hardware and can plug into tools like email, chat, calendars, and code repositories. A minority report meaningful wins — especially for non-programmers and small businesses — in areas like personal assistants, note and task automation, data digests, and lightweight back-office workflows, but even they describe high setup friction, brittleness, security concerns, and significant token costs. Many others argue that most touted use cases are better solved with simpler, deterministic scripts or built-in LLM tools, seeing OpenClaw more as a FOMO-driven experiment than a mature, broadly useful platform today.

Overall sentiment

  • Thread is sharply divided: a minority report real, ongoing value from OpenClaw‑style agents; a large number found it fragile, overhyped, or redundant.
  • Many technically inclined users conclude they can do the same or better with scripts, cron jobs, and “agentic coding” in Claude/ChatGPT/Codex.
  • Several posters see OpenClaw more as a cultural/FOMO phenomenon (similar to NFTs/crypto) and a way to burn tokens than a mature tool.

Enthusiastic use cases

  • Personal assistant via chat (Telegram/WhatsApp/Discord/Matrix):
    • Daily or morning briefings from email, calendar, HN/Twitter, RSS, GitHub, etc.
    • Todo management, reminders, and rolling over tasks across days.
    • Calorie, workout, weight tracking; simple journaling and idea capture.
    • Language learning practice and role‑playing exercises.
  • Knowledge and note workflows:
    • Deep integration with Obsidian/Markdown/Trilium wikis as “second brain” and long‑term memory.
    • Automatic flashcard generation and spaced repetition support (sometimes wired into custom or Anki‑style apps).
    • Family history collection and archiving through ongoing chat.
  • Business and operations:
    • ERP bugfixing pipeline, Jira → PRs → AI review.
    • Data analyst/marketing agents: ad creative analysis, funnel analysis, campaign reports.
    • Support triage, internal helpdesk, email monitoring and routing.
    • Proposal generation: from photos + forms to 10–30 page PDFs and email drafts.
    • Home‑lab/server management, media servers, home automation control.

Skepticism and criticism

  • Many report OpenClaw as janky, “15% broken” at all times, with integrations (Slack/Discord/WhatsApp) especially unreliable.
  • Common pattern: impressive demos the first 1–2 times, then cron jobs fail, tasks get forgotten, or self‑reported “fixes” don’t actually work.
  • Strong concern over non‑determinism: tasks that “should” be simple (e.g., todo rollover, scheduled checks) behave unpredictably.

Security, cost, and reliability concerns

  • Repeated warnings about giving an LLM harness broad access to personal email, files, APIs, or bank‑like resources; prompt‑injection risk is highlighted.
  • Some horror stories: broken user accounts, deleted files/repos, system lockouts.
  • Token costs can reach tens or hundreds of dollars per month with powerful models; some saw provider policy changes break previously working setups.
  • Several users sandbox OpenClaw (VPS, containers, separate accounts) and still find it too brittle or high‑maintenance.

Alternatives and DIY patterns

  • Many migrate to:
    • Claude Code/Codex + cron/remote control/channels.
    • Lighter harnesses (NanoClaw, Hermes Agent, Town, Atmita, custom frameworks).
    • Local models via Ollama, Gemma, Qwen, etc.
  • Common stance: use LLMs to generate deterministic scripts/services, then automate those, rather than running a fully autonomous agent.

Meta: hype, bots, and adoption

  • Several doubt organic adoption, pointing to GitHub stars, social media astroturfing, and “course grifters.” Others say they see real internal usage at companies.
  • Some treat strong OpenClaw evangelism as a signal to mute/block accounts in the “AI hype” space.
  • Overall, participants expect “proactive agents” to become important eventually, but see OpenClaw as an early, brittle, and security‑weak exploration rather than the final form.