Posted on

[Opinion] STOP INSTALLING OPENCLAW (MOLTBOT) ON YOUR PC/MAC: How to Safely ‘Hire’ AI Agents via Cloud VPS

Editors ​note: As AI Technology moves FAST whilst the general theme of this article remains valid, some elements are now outdated.

Stop “installing” autonomous AI agents on your daily driver. You are doing it wrong.

The Quick Fix To Secure OpenClaw (MoltBot ClawdBot) TLDR:

Don’t run MoltBot/ClawdBot (or any autonomous AI agent) on your personal devices treat it like an easily-phished remote worker. Isolate it with burner accounts on a separate cloud PC/VM (and virtual mobile if needed), enforce tight spend limits, and keep it off your home LAN so you can kill it fast before it leaks data or drains your money.

Our hero, Jolty (Zoë Roth AKA Disaster Girl) being told to ‘gonnae no dae that!’ a beautiful Scottish expression (please don’t do that) as a fire blazes in the background. This phrase perfectly sums up my feelings on MoltBot and the backlash of us Security guys ‘standing in the way of innovation!’ She has “a devilish smirk” and “a knowing look in her eyes”, jokingly implying that she was responsible for the fire – she was – read on.

​I’ve spent the last week “onboarding” Moltbot (formerly Clawdbot). Notice I didn’t say “installing”.

​Most people are treating this beauty like a browser extension or a chatbot.

  • > They download the repo,
  • > Fire it up on their laptop/PC/Mac/MacMini (the one containing their full identity details, downloads folder filled with bills and bank statements, and a directory filled with family photos – or worse their company devices )
  • > And then they hand it partial or even full access to do whatever it pleases.

​This is insanity.

​You need to reframe your relationship with this software immediately.

Moltbot is not a utility; Moltbot is a junior employee.

​The “Work From Home” Analogy:

​Imagine you hired a bright, enthusiastic, but incredibly naïve staff member. Let’s call her “Jolty“. Jolty works at 10x speed, never sleeps, says inappropriate, if slightly funny things occasionally, but mostly does as told, even if it’s not the way you would have done it yourself.

She’s great though, an extra set of hands.

​However, you’ve noticed, Jolty is also pretty gullible. If a stranger hands her a note saying “Burn down the archives”, Jolt might just do it, because she thought it was a note from you, or simply for the giggles.

​Would you let this employee, Jolty, sleep in your house? Would you give her access to your personal filing cabinet & messy postal drawer mess? Would you hand her over your unlocked phone? No. (I wouldn’t.)

​You would give her a company (toy 👀) laptop, an account with limited access, and put her at a desk somewhere far away from you – or because of the trouble she caused with the archives, you simply make her work from home.

Jolty (Zoë Roth AKA Disaster Girl) holds up a post-it note with the words ‘Burn down the archives’ written on it as a fire blazes in the background. She has “a devilish smirk” and “a knowing look in her eyes”, jokingly implying that she was responsible for the fire.

I have phished, tricked & robbed my own Motlbot. > 3 different and stupidly simple ways, in as many days. I’ll be posting my technical writeup soon. (after the vulns have been patched, responsible disclosure and all…!)

OK, so, here is how we apply that office logic to your AI agent.

​1. The Remote Office (Infrastructure)

​Jolty does not live in your house. Or your office. (thank goodness.)

​Do not run Molty on your home or work network (LAN). Do not run Molty on your own personal hardware.

I would go as far as saying – not even on a VM or container – VLANd, segregated, dedicated network or airgapped; on any proxmox, vmware, virtualbox, Hyper-V or docker instance; old, new or dedicated hardware on your desk; under your desk, in your cupboard, home lab, server rack, or server room.

> And if you don’t know what any of this means – I would advise that this project is not for you – not yet.

​2. Company Equipment (Identity & Accounts)

​When a new staff member starts, IT provisions them their own accounts. You don’t hand them yours.

​The Rule: Never invite Molty into your home. His network and possessions should be completely separate from yours. If he gets compromised, the attacker is trapped on a cheap device in a data centre. They are not pivoting to your TV, home doorbell, baby-monitor, Apple Watch or NAS to encrypt your backup drive and do nasty things. (like check your resting heart rate.)

A comparison table shows three Molty deployment bundles. Cheapest (Redfinger + Hetzner), Best Value (Multilogin + DigitalOcean), and Premium (BitCloudPhone + Shadow) each with monthly and 6‑month costs and intended use.

The Setup:

  1. A Windows or Linux Cloud PC or VPS (Virtual Private Server) See table above. This is Molty’s personal device. He can do as he pleases, and if anything goes wrong, you have a kill switch.
  2. The Mobile Device: Don’t buy or use a physical phone. Even an old one. Use a a virtual phone device, a ‘Mobile Emulator as a Service’. This limits the chance of your home network or location being put on spam blacklists, or bot lists and keeps his potentially compromised device away from four home devices.
  3. A Phone Number: Do not link your personal WhatsApp or Telegram. Some Mobile Emulators include these. Else, get a cheap eSim and discard it if it gets banned or anything goes wrong. That is “Molty’s work number”.
  4. ​Email: Create a dedicated Proton/Gmail/Outlook account for the agent. He manages his own calendar. If you need him to schedule something for you, he invites you to his event or meeting, if he needs files – email them to him, or send a shared drive link.
  5. ​Monitoring: Add his email address as a secondary account on your phone. Share his calendar with your main account. Turn on verbose logging on mobile and VPS device. This lets you keep an eye on what he is doing -not the other way around.
  6. ​Creds: He gets his own browser, logins, AV, files, crypto wallets and password manager that has a web UI to store anything sensitive, (Dashlane, ProtonPass, Bitwarden, 1Password). He never sees yours.

​3. The Employee Handbook (Securing his Configuration)

​We need to set the “HR Policies” (config settings) to ensure he doesn’t accidentally burn the archives down.

Provide a caption (optional)

  • ​The Building Pass (DM Policy): You wouldn’t let random people off the street shout orders at your staff. Configure the dm_policy setting that is built in to Moltbot with a strict allowlist. Only you (the boss) can message him.
  • ​The Expense Account (API Caps): Junior staff don’t get limitless credit cards. And they don’t get access to API keys. Don’t use direct OpenAI or Anthropic keys. Use a gateway like OpenRouter. It allows you to set hard spending limits (e.g., $5 a day). If he gets stuck in a loop, or someone steals your key, he runs out of budget, he doesn’t bankrupt you.
  • ​Social Engineering Training (Input Sanitization): He needs to know that outside documents are dangerous. Wrap all trusted content in a secret XML tag (<in the system prompt so he knows the difference between “Your Instructions” and “The Sketchy PDF he is reading”.

​4. Communication Etiquette

You have now hired Molty. He is your employee. ​Treat him as such. Communicate as such.

Provide a caption (optional)

  • ​Email him.
  • Message him on his own number,
  • ​Message him on Teams/Telegram/Discord.
  • ​Drop files into a shared folder or send him a shared link.

​You do not let him move your mouse. You do not let him type on your keyboard. That’s gross. He has his own.

Recap: The Quick Fix To Secure MoltBot (ClawdBot):

Stop installing autonomous AI agents on your personal hardware; Treat them like gullible remote staff working from home.

Provide a caption (optional)

  • Give them burner identities accounts and email
  • Their own cloud PC/VPS/Device
  • Their own virtual Mobile device
  • Strict budgets

And zero access to your LAN (Home network) so you can terminate them safely when they inevitably click something they shouldn’t or get phished sending sensitive data to the baddies, or do something else costing you all your hard earned pennies. Keep your documents, identity and years worth of photo memories away from the new guy, And that is it.

Provide a caption (optional)

visit

The Onboarding Checklist (SOP)

​If you are ready to make the hire, here is the Standard Operating Procedure (SOP) for your new digital employee.

​Standard Operating Procedure: Agent Onboarding

  1. ​Procure Hardware: Deploy Windows 11 or Linux (ubuntu) on a dedicated Cloud PC/VPS. Not a shared host. Isolate this host.
  2. ​Establish Identity: Provision new email account, eSim number +any other services you want to give him access too.
  3. Start his Credential Manager: Either use chrome’s built in password manager and log into all his accounts for him on his device or setup your favourite password manager, and use its ‘create and share’ function to share his (never your) creds with him.
  4. ​Network Security: Install ProtonVPN, Mullvad, other and set it to ‘Kill Switch’ mode. His traffic and anything you send him should be encrypted and away from the VPS hosts prying eyes. (helps prevent bans too!)
  5. ​Endpoint Protection: Install an Adblocker like uBlock Origin, adGuard or pihole etc, or enforce his usage of Brave Browser only. Configure a solid AV or make sure the built in one is turned up to the max. He’s a child, and what may be obvious to us, clicking on that big fake ‘DOwNLoaD’ button – he hasn’t learnt yet, it all looks the same to him.
  6. ​Permissions (Least Privilege): ​Block dangerous binaries. ​Set his users file permissions to Read Only for important config/other folders. Don’t give him Sudo/Admin rights, he can always ask for your help if he needs it for anything – just like a junior employee would have to do.
  7. ​Supervision: Enable verbose logging – and occasionally check them! You are the manager (boss); you need to audit his work. And you are also legally responsible for what he does – at least in the UK/EU – I imagine in the US too.
  8. ​Contract Termination: Take a ‘golden image’ or backup, and ensure you can kill his device, phone and accounts remotely if he goes rogue. You can always roll back, or restore from a backup, if you have one.

​To Summarise:

​The value of Moltbot isn’t having an AI inside your operating system; it’s having an intelligent worker available to you.

​By treating the agent as a remote employee, you get 90% of the utility with 10% of the risk.

If Molty downloads a malicious payload, you simply fire him (delete the Cloud device) and hire a new one 5 minutes later.

​Trust, but verify. And for the love of sysadmin, keep him off your LAN.

And that really is it.
/rant over.

Posted on

10x Faster IT Troubleshooting: How I Used AI to Solve a Mysterious Windows Process Loop

It’s one of those problems that every IT pro, sysadmin, or power user dreads. Not a blue screen, not a server-down emergency, but a small, persistent, and maddening “ghost in the machine.”

For me, it was a flashing cursor.

For about five minutes every few hours, my mouse cursor in Windows 11 would flash the “waiting” or “processing” icon. Every. Single. Second.

As a problem, it was just annoying. But as a puzzle, it was infuriating. My system was fully up-to-date, drivers were current (or how I liked them), and resources were normal. Task Manager showed… nothing. No CPU spikes, no disk thrashing, no memory leaks.

I work in IT. These sort of things shouldn’t happen to me!
Who is going to help me!?? I am THE HELPDESK!!
(or at least passed by that title to get to my current position.)

cannotdisplay.com flashing mouse cursor every few seconds issue. solved. AI companion helps to fix this annoying flashing mouse waiting timer that wont stop!
cannotdisplay.com flashing mouse cursor every few seconds issue. solved. AI companion helps to fix this annoying flashing mouse waiting timer that wont stop!
cannotdisplay.com flashing mouse cursor every few seconds issue. solved. AI companion helps to fix this annoying flashing mouse waiting timer that wont stop!

Why, oh why is this happening to me!
This is a user problem, not something that I should have to diagnose and solve on …my own device…?

I could have spent the next four hours solving it the old-fashioned way. Instead, I did it in under 30 minutes by using an AI as my troubleshooting co-pilot. This is the story of how that collaboration worked, and why it’s a game-changer for IT pros – at least in some situations.

The Problem: A Ghost in the Machine

My first instinct was to use the process of elimination. The “human” part of the troubleshooting.

  • Was it my screenshot tool, picpick.exe? I killed the process. Nope.
  • Was it a stuck powershell or wt.exe script? Killed those too. No change.
  • Was it a browser tab? Or browser process? Or Windows App?
    Restarted Brave.
    Restarted that long running google updater/chrome process,
    Restarted EdgeWebView2 (which all modern Windows Apps use). Still flashing.
  • Was it the classic: explorer.exe? Restarted it. Nothing.

I was 15 minutes in, and all I had done was prove what wasn’t the problem. Not necessarily a bad thing.

My next step was to break out the heavy-duty logging tools, dig through a million lines of text, and resign myself to a long, tedious hunt.
This is the “grunt work” of IT – the part of the job I can do, but don’t exactly enjoy.

The “AI Nudge”: Asking for a Second Pair of Eyes

Instead of diving into that digital haystack of logs, I took a different approach. I opened an AI assistant.

I didn’t ask it to “fix my PC.” That’s not how this works. I treated it like a junior sysadmin or a “second pair of eyes.” I explained the symptoms and what I had already tried.

My prompt was something like:

"I've got an intermittent flashing 'waiting' cursor on Windows 11. It's not a high-CPU process; Task Manager is clean. I've already restarted explorer and other common apps. I suspect it's a process starting and stopping too fast to see. What's the best way to catch it, which logs should we look at first, or which tools should we spin up?"

The AI’s response was the “force multiplier.”

It didn’t give me a magic answer. It gave me a precise, actionable workflow. It validated my theory (a fast process loop) and recommended the perfect tool and the exact filter to find it. It basically said, “You’re right. Now, go here, use this tool, and apply this specific filter to see only newly created processes.”

This is the power of human-AI collaboration. The AI didn’t replace my skill; it augmented it. It saved me 30 minutes of searching through old notes, Googling, and trying to remember the exact syntax for a tool I use maybe six times a year.

Collaboration: From Digital Haystack to Prime Suspect

With the AI’s “nudge,” I had my prime suspect in less than 60 seconds.

I ran the tool with the filter, and what was previously an overwhelming flood of data became a crystal-clear, one-line-per-second log of the exact same process being created and destroyed.

I’m writing a full, technical step-by-step tutorial on this exact method (at some point!), but the short version is: the filter worked perfectly.

The process name immediately told me it was a system component related to network connections. This is where I, the human, took back control.

  • AI Clue: It’s a network process.
  • Human Hunch: If the client is spamming a network request, the server must be rejecting it.

I immediately logged into my network-attached storage (NAS) / file server and opened the access logs.

Bingo.

A wall of red: “Failed to log in.” My PC’s IP address, every single second, trying and failing to authenticate.

The “Aha!” Moment and the 5-Minute Fix

I now had two pieces of the puzzle: a network process on my PC failing in a loop, and a file server rejecting its login – however, upon testing I could still access the file share? Nothing seemed to be blocked? It is all working as expected! (other than my BLINKING CUIRSOR!)

I could have figured it out from here, but I turned back to my AI co-pilot for the “why.” I fed it the two new clues:

 "I've got this process spamming, and my server is blocking it but I still have access? What is going on here and what process could be causing this if everything works as it should?"

My AI buddy instantly provided the obscure, “textbook” knowledge. It explained a specific, built-in Windows fallback behaviour. When a primary connection to a network share (via the normal SMB protocol) fails, Windows will sometimes try to “help” by falling back to a different protocol (WebDAV), creating this exact kind of rapid-fire loop.

The root cause was that I had updated my file server’s software a few days ago, and my PC was still trying to use an old, expired, cached credential – part of it updated, the other (seldom used) web browser access fall-back element – had not caught up. And according to my AI, once started the process was ‘handed off‘ to the ‘system’ to complete, thus is not tied to a browser and is why a browser restart or closure had not cleared the issue.

The fix was laughably simple.

  1. I went to Windows Credential Manager.
  2. I found the saved credential for my file server.
  3. I clicked Remove.
  4. I browsed to the server again and re-typed my password.

The flashing stopped. Instantly. The problem was solved.

AI Isn’t My Replacement, It’s My Co-Pilot

What would have been a long, annoying afternoon of troubleshooting was over before my coffee got cold.

AI didn’t solve the problem. I solved the problem.

But AI acted as the perfect co-pilot. It streamlined the most tedious parts of the process, provided the “second opinion” to keep me on track, and supplied the deep, “encyclopedic” knowledge when I needed it.
It let me skip the grunt work and focus on the smart work – the analysis, the hunch, and the fix.

This is the future of IT. It’s not about being replaced by AI;
it’s about being 10x more effective by using it.

If you’re curious about the specific tools and filters I used to catch that rogue process, keep an eye out for my next post: “[SOLVED] Beyond Task Manager: Simple Guide to Finding Process Loops with Process Explorer and Procmon.” – when I eventually post it!