Yeah, i’ve gone to the point where I will just stop reading AI posts after a paragraph or two if there are no specifics. The “it works!” / “no it doesn’t” genre is saturated with generality. Show, don’t tell, or I will default to believing you don’t have anything to show at all.
That was very vague, but I kinda get where they're coming from.
I'm now using pi (the thing openclaw is built on) and within a few days i build a tmux plugin and semaphore plugin^1, and it has automated the way _I_ used to use Claude.
The things I disagree with OP is: The usefulness of persistent memory beyond a single line in AGENTS.md "If the user says 'next time' update your AGENTS.md", the use of long-running loops, or the idea that everything can be resolved via chat - might be true for simple projects, but any original work needs me to design the 'right' approach ~5% of the time.
That's not a lot, but AI lets you create load-bearing tech-debt within hours, at which point you're stuck with a lot of shit and you dont know how far it got smeared.
They're not coming from anywhere. It's an LLM-written article, and given how non-specific it is, I imagine the prompt wasn't much more than "write an article about how OpenClaw is changing my life".
And the fact this post has 300+ comments, just like countless LLM-generated articles we get here pretty much daily... I guess proves the point in a way?
That’s another reason there just isn't any point in looking at these articles anymore unless they take you on a trip deep in the weeds of some specific problem or example. We need deep case studies (pro and con), not bulleted lists and talking points.
My agents get auto-injected with the core spec via pi-extention.
I have an idea, agent turns it into a draft, depending on idea vagueness/complexity combination of: Looking for alternative, plan the change, look for alternative, split up into smaller drafts to drive separately, execute change (spec, code, tests), review change.
Usually its just: Draft, plan, exec, commit. The steps are flexible enough. Usually each step is a different agent, sometimes not. On complex builds or big changes, a planning agent itself might spawn subagents to avoid bloating its own context.
The progress is stored in: ./dev/{draft/<n>.md , wip/<n>/, fin/<n>/ }.
My `lead` pi has a separate AGENTS.md with how to organize the above sequence, and some notes on how to prompt, keep things small, etc. Note that its skill `tmux-coding-agrents` calls other pi instances (optionally set to codex). I've moved off the claude cli entirely.
I used to spend time telling claude not to forget updating the specs or building its tests because context bloat made them forget AGENTS.md, or to read certain files before it should execute a plan. The lead agent does this just fine now, and every time i see it make a mistake i say: "Next time do X" and it automatically updates its own or the worker agents AGENTS.md.
Because my lead agent context is all about managing this process it doesn't forget steps while its off chasing some bug.
Also, I build (but did not publish) a pi plugin that attempts to use other accounts on usage limits.
Most surprising moment I had, was my lead spawning a subagent, spawning a subagent, which spawned a tmux-bash build with very little prompting, and it was the right thing to do to prevent each agent from context bloat.
Thanks for the write up. I'm starting to consider enhancing my setup and building on pi sounds interesting. I have a similar core workflow, but I'm still tied to CC's interface and I can see how it might be nice to have something a bit more custom.
- the smaller context and default-off for thinking make it extremely fast (thinking is a dead-end bitter lesson imo)
- the source is available; and organized specifically to make it easy for agents to write and test extensions. Just launch pi in the pi-mono directory, and it will turn your idea into an extension in no time.
There is no code, there are no tools, there is no configuration, and there are no projects.
This is an AI generated post likely created by going to chatgpt.com and typing in "write a blogpost hyping up [thing] as the next technological revolution", like most tech blog content seems to be now. None of those things ever existed, the AI made them up to fulfill the request.
> There is no code, there are no tools, there is no configuration, and there are no projects.
To add to this, OpenClaw is incapable of doing anything meaningful. The context management is horrible, the bot constantly forgets basic instructions, and often misconfigures itself to the point of crashing.
There is zero evidence this is the case. You are making up baseless accusation, probably due to partisan motivations.
edit: love the downvotes. I guess HN really is Reddit now. You can make any accusation without evidence and people are supposed to just believe it. If you call it out you get downvoted.
It doesn’t work like that. The burden is on the person making the claim. If you are going to accuse someone of posting an AI-written article you need you show evidence.
It's a losing strategy in 2026 to assume by default that any questionable spam blog/comment/etc content is written by an actual human unless proven otherwise.
Besides, if there are enough red flags that make it indistinguishable from actual AI slop, then chances are it's not worth reading anyway and nothing of value was lost by a false positive.
What evidence are you expecting exactly? It's vacuous AI slop that spends 1000 words just making vague assertions about how incredible OpenClaw is without a single actual example. There's nothing here, it's not real. You are going to struggle going forward if you can't detect AI slop this obvious.
Exactly. Posts that say "I got great results" are just advertisements. Tell me what you're doing that's working good for you. What is your workflow, tooling, what kind of projects have you made.
>Over the past year, I’ve been actively using Claude Code for development. Many people believed AI could already assist with programming—seemingly replacing programmers—but I never felt it brought any revolutionary change to the way I work.
Funny, because just last month, HN was drowning in blog posts saying Claude Code is what enables them to step away from the desk, is definitely going to replace programmers, and lets people code "all through chatting on [their] phone" (being able to code from your phone while sitting on the bus seems to be the magic threshold that makes all the datacenters worth it).
Yeah… I'm using Claude Code almost all day every day, but it still 100% requires my judgment. If another AI like OpenClaw was just giving the thumbs up to whatever CC was doing, it would not end well (for my projects anyway).
Yes. Programmers might be especially susceptible precisely because our advanced understanding makes us think we cannot be easily fooled.
But we are also easier to impress: only we understand how difficult it is to one-shot code a working app.
AI psychosis sets in when AI captures enough of your perception to alter your reality. Programmers might be "smarter", but we give AI a bigger set of tools to capture our perception with.
And then there's the fact that we want to be fooled.
We are also used to prioritizing "flow states" as part of our engagement with technology, and these tools seem to be flow-state inducers. Also prone to following hype, used to typing words into computers to get results, etc...
"Flow-state inducers" is interesting, and I think you're onto something. There's something so satisfying about getting working code so easily, feeling like you're jumping from one solution to the next.
Did they even end up launching and maintaining the project? Did things break and were they able to fix it properly? The amount of front-loaded fondness for this technology without any of the practical execution and follow up really bugs me.
It's like we all fell under the spell of a terminal endlessly printing output as some kind of measurement of progress.
It makes me sad that there are so many of these heavily-upvoted posts now that are hand-wavey about AI and is itself AI-generated. It benefits everyone involved except people like me who are trying to cut through the noise.