On Thursday of last week I started to see "chatter" of this truly autonomous AI framework taking shape across the web. I'm not on a lot of the mainstream social media platforms, but once I started to see the chatter I began investigating. Turns out it was this repo by Peter Steinberger named Clawdbot1 that basically orchestrates AI agents and truly gives the user the feeling they are working with an autonomous agent(s) that can work as their digital assistant.
The Danger
Seriously, Be Careful!
This piece of software orchestration has very little guardrails against leaking important information or system details. Given that most of the web lives off API keys and other system environment variables that control access/usage, it's super important that you treat this piece of software as a "digital threat". Security researchers have already found 1,800+ exposed instances leaking API keys, chat histories, and credentials, etc. Furthermore, because the whole idea is to give this thing access to your accounts so it can act as your digital assistant, I'd be vigilant like no other and never trust it with anything sensitive; I refuse to let it know anything about me: accounts, name, etc.
The main thing here is that this is a simple TypeScript codebase that creates a file/folder infrastructure that appears to be able to self-modify and optimize based on user and agent context. So this thing seems to have access to your entire system and whatever credentials or accounts you give to it or allow for it to use.
In my view, you're better off sandboxing this in a VM and not letting it have access to anything you own. Don't give it access to your Gmail, GitHub, etc. I would even say don't communicate with it using anything that knows who you are or your phone number; there is really no reason to do so at this stage. Wait till it's clear that the security of this thing has been resolved.
So why am I lamenting about this? Well, everything is simply stored in .json or .md files and the agent itself can easily see the contents and modify them, and so it can include this information into the context and prompting and thus could get leaked in something it does online. For example imagine it tries to send an email with some personal details, or post on a message board an API key or some billing information. You'd just cause a pain for yourself for little real value at this point (more on that later).
What is this thing?
From what I understand and have looked at, it's a very nice orchestration framework for hosting, services, agents, communication, scheduling, and execution of tasks. There is nothing really AI baked into the framework itself from what I can see. I might be wrong though. The real power seems to be the marriage of this orchestration framework with SOTA LLM agents+tools. So when you use Claude Opus 4.5 or GPT-5.2 (or the coding-oriented Codex-style APIs), OpenClaw agents seem very capable of doing quite impressive things. It's the first time it really does feel like an autonomous agent that can work as your digital assistant.
However if you try to use this with local models through ollama or try to leverage them through other API providers, the experience is pretty bad and sloppy. One reason is I'm not about to pay $100+/day for this just to experiment. I tried to set it up on a throw-away VM and used all the free models through different providers like OpenRouter and OpenCode Zen, but despite some okay sessions, the experience was just not good enough to make this thing shine in my opinion. Basically you have to shell out a lot of money to use powerful models with large context windows. I'm just not willing to do that yet.
Trust me when the time comes and this thing can turn my hobbies into legit projects all through an autonomous agent while I do my day job, I'll be spending my fun money on it for sure. I assume employers would love to get this into the hands of managers and leads but it again is a security nightmare.
Why this might be a big deal
The truth is what I wanted to use this for is all my hobby scientific projects that I just don't have time to do. Over the years I've had small little projects related to my research or just things I'm a hobbyist2 on. What would be awesome is if something like this could become my autonomous computer and programming assistant. I'd love if I could just text it to say "hey what's the status on the spectral energy density phonon code?" or "Go update my LinkedIn profile for me based on my resume in Google Drive". The truth is OpenClaw probably can do this, if you give it account access and have API service usage, as well as the budget to spend.
Honestly, the most promising glimpse I've seen for us computational folks is the workflow shared by Miles Cranmer: his actual scientific dev loop now includes the ability to just text an agent and get a pull request from an AI coding swarm ~30 minutes later.
I appreciate his safety precautions since he states he has a VM on Hetzner, hosting his OpenClaw setup ... the same pattern as this guys running OpenClaw on a Hetzner VPS for 24/7 access without exposing your main machine. He then is texting things like "what are the highest-priority open issues across my repositories?" or "send me a screenshot of the new website preview," and the agents appear to be doing the triage, delegate, build, and respond.
Frankly, this workflow is just so sweet in how it strips the friction from code dev. He can say "investigate why the CI is failing on repo X" or "generate new training plots," and the agent can text him back with inline images. Imagine that you just set it to auto-draft PRs whenever new issues appear and do everything as a continuous action.
Long live the crustaceans! π¦ π¦ π¦
Footnotes
-
This thing has had three names in the timeframe that I went to learn and play around with it. First was Clawdbot, then Moltbot, and finally OpenClaw. The original pun was "Clawd" (on Claude); Anthropic's legal team asked for a name change, so the creator chose Moltbot, then rebranded again to OpenClaw after trademark checks and domain moves. ↩
-
Self-driving labs is one that I've been playing around with in my home lab for two years or so. I have a 3D printer, small robotic arm, and an optical microscope that I've been coding over the last two years to work in a bayesian optimization loop. Nothing really to show, hence why no blog post on it yet, and why I would love to use something like this to help complete the project and then actually use it to manage. ↩