Somehow, I feel like I’m converging onto this. I built https://github.com/rcarmo/webterm as a quick solution to the “multiple agents” problem and https://github.com/rcarmo/piclaw started out as a mobile UX for a simpler, tighter “claw” and has been slowly morphing into an IDE (I just shipped UI extension support and have refactored the CodeMirror editor into an extension, and I suspect a terminal is next as well as a few custom viewers/editors). I spend more time inside piclaw’s web app on my desktop than VS Code now…
Hmm. OK, I guess. But I are you going to stick to just OpenClaw, or look into variants? (I created https://github.com/rcarmo/piclaw, which is a leaner, less hype-driven and more utilitarian thing)
I started using it _way_ before it was even mentioned in AI projects. The key reasons I stuck with it were: 1. As a Pythonista, I _very_ much like its batteries included philosophy (I get proper Typescript, SQLite and a lot of goodies out of the box without hundreds of crufty NPM plugins) and 2. The tooling is awesome: a decent bundler, ability to build "single file" executables, etc.
If you think it's popular because of AI, think again.
I didn't say I thought it was popular because of AI. I clarified whether this mental link could be faulty because a lot of new projects are AI-related in general.
I might give it a shot soon. Would you recommend it for simpler all-in-one web projects that don't utilize most of the vast array of tools it includes? Or is it more suited to the heavy-weights?
I am making sure that the development instance doesn't wipe itself when testing. There are test guidelines to use a :memory: fixture, but Claude Opus is an idiot and I can't trust it--Codex is much more sane about such things.
I think this is actually cool, but that it should use Apple’s own local models by default to minimize the AI usage footprint. They are capable enough to do filing suggestions.
reply