mahendra0203

OpenClaw feels like early React" is a great framing but I think it leads to the wrong conclusion. React didn't win because Next.js showed up. React won because the component model was right, and then people built whatever they needed on top of it.

The risk with "framework on top of framework" is you inherit both set s of opinions AND both sets of bugs.. When OpenClaw updates, does DenchClaw break? When DuchDB has a quirk, is that your bug or theirs? The dependency chain gets real deep real fast.

Copying someone's entire Chrome profile is bold. Like, really bold. That's a massive ask. "DenchClaw sees what you see" is either the most powerful pitch or the scariest pitch, depends on who you talking to.

Freezing JS execution between actions is the kind of obvious idea that nobody did properly untill now. Kudos for actually forking Chromium instead of hacking around Playwright like everybody else.

But here's my thought: you're solving the "stale state" problem by making the browser deterministic. Real websites aren't deterministic. WebSOcket pushes, long-polling, background fetches, animations that don't finish — freezing execution doesn't pause the server. The moment you unfreeze, the world may have moved.

90.5% on Mind2Web is great. But Mind2Web tasks are mostly "fill a form, click submit." The brutal failures happen on SPAs with optimistic UI updates, where the DOM says "saved" but the network request hasn't finished. Does ABP handle that case, or does the freeze just delay the confusion?

Genuine question — not trying to tear this down. The architecture is smart. I just wonder if "make the browser simpler for the agent", eventually hit s a wall where you need to make the agent smarter about async instead.

Honestly? Don't think you don't need to rewrite your CLI.

The whole "raw JSON > flags" argument sounds clean in a blog but falls apart in practice. Agents are actually good at parsing messy human output. stderr, exit codes, even tables.

I run AI agents against CLIs every day. The failures are almost never, "the outpt wasn't structured enough." They're context window overflows, permission issues, and the agent confidently running the wrong command over and o ver.

The real insight here shouldn't be "rewrite for agents" — it's "make your CLI not actively hostile." --output json and non-zero exit codes on failure. That's should be it.

Maybe we are optimising the wrong layer..