I love OpenClaw and what it can do. I have long been wanting OpenClaw to take care of my shopping and purchases online. However, with the current threat of prompt injections, I do not trust it with my credit card details as it stands.
To reduce the chance of breaches, I built ClawLock, a supervisor (sidecar with process isolation) for OpenClaw that injects controls around tool use. The user defines a passport for what the tools can and cannot do and ClawLock governs it. For high-risk transactions like in-browser purchases or shell command, a deterministic policy engine and an LLM-as-judge are used to detect any potential threats prior to execution.
ClawLock is currently in its infancy. It is primarily tested on Linux. I would appreciate any feedback on your experience using it on MacOS and WSL.
I am in strategy consulting and I can tell you the productivity gains are real in terms of research, model building, and summarising work. The result is price pressure from our clients.
This is really cool, nicely done. Q: How did you get the WhatsApp integration working? I thought that was completely closed off unless you are in Europe.
Can you please not post like this, especially in Show HN threads? It's good to let people know when your attempt to use their software runs into problems. But please do it in a helpful way, not a dismissive way.
Besides being a fiction very much supported by dictators, international law is a delusion entertained by (a) those who have never lived under a dictatorship and (b) those oblivious to the fact that their freedoms and peace depend on the protection of the world’s most powerful military.
Which is unfortunate, but a consequence of Microsoft's perennial, embrace, extend, extinguish - they embraced instant-messaging version 3 (or wherever we are now), and they're onto the extend part - extending Teams' reach by bundling it 'for free' in Office, and the OS, so people don't "need" to buy Slack.
Slack won't be 'extinguished' but it will have a falling market share, despite the dumpster fire that is Teams, and the bean-counters in most corporations getting kudos from their bosses for 'cost savings'.
Frequently fails to connect, doesn't honor system audio device settings and frequency forgets its own, frequently fails to mark messages as read, sometimes even after hitting "Mark all as read," sometimes fails to send notifications on new chats, especially on my phone.
It's the least reliable chat program I've ever used.
To reduce the chance of breaches, I built ClawLock, a supervisor (sidecar with process isolation) for OpenClaw that injects controls around tool use. The user defines a passport for what the tools can and cannot do and ClawLock governs it. For high-risk transactions like in-browser purchases or shell command, a deterministic policy engine and an LLM-as-judge are used to detect any potential threats prior to execution.
ClawLock is currently in its infancy. It is primarily tested on Linux. I would appreciate any feedback on your experience using it on MacOS and WSL.
reply