Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenClaw – Moltbot Renamed Again

openclaw.ai

Post reply on HN
Print view View original

331–340 of 422 posts

Re: OpenClaw – Moltbot Renamed Again

#333

Post by drewstiff »

guluarte wrote: post #230
lode wrote: post #67

I tried it out yesterday, after reading the enthousiastic article at https://www.macstories.net/stories/clawdbot-showed-me-what-t... Setting it up was easy enough, but just as I was about to start linking it to some test accounts, I noticed I already had blown through about $5 of Claude tokens in half an hour, and deleted the VPS immediately. Then today I saw this follow up: https://mastodon.macstories.net/@viticci/1…

you can use your claude max subscription

No you can't, Anthropic keep blocking it

Re: OpenClaw – Moltbot Renamed Again

#337

Post by rizzo94 »

woodylondon wrote: post #51

My biggest issue with this whole thing is: how do you protect yourself from prompt injection? Anyone installing this on their local machine is a little crazy :). I have it running in Docker on a small VPS, all locked down. However, it does not address prompt injection. I can see how tools like Dropbox, restricted GitHub access, etc., could all be used to back up data in case something goes wrong. It's Gmail and Calen…

I ran into the same concerns while experimenting with OpenClaw/Moltbot. Locking it down in Docker or on a VPS definitely helps with blast radius, but it doesn’t really solve prompt injection—especially once the agent is allowed to read and act on untrusted inputs like email or calendar content.

Gmail and Calendar were the hardest for me too. I considered the same workaround (a separate inbox with limited scope), but at some point the operational overhead starts to outweigh the benefit. You end up spending more time designing guardrails than actually getting value from the agent.

That experience is what pushed me to look at alternatives like PAIO, where the BYOK model and tighter permission boundaries reduced the need for so many ad-hoc defenses. I still think a community-maintained OpenClaw security playbook would be hugely valuable—especially with concrete examples of “this is safe enough” setups and real, production-like use cases.

Re: OpenClaw – Moltbot Renamed Again

#340

Post by whatevermom5 »

rizzo94 wrote: post #337
woodylondon wrote: post #51

My biggest issue with this whole thing is: how do you protect yourself from prompt injection? Anyone installing this on their local machine is a little crazy :). I have it running in Docker on a small VPS, all locked down. However, it does not address prompt injection. I can see how tools like Dropbox, restricted GitHub access, etc., could all be used to back up data in case something goes wrong. It's Gmail and Calen…

I ran into the same concerns while experimenting with OpenClaw/Moltbot. Locking it down in Docker or on a VPS definitely helps with blast radius, but it doesn’t really solve prompt injection—especially once the agent is allowed to read and act on untrusted inputs like email or calendar content. Gmail and Calendar were the hardest for me too. I considered the same workaround (a separate inbox with limited scope), but…

AI slop
Post reply on HN