Clawdbot

Yesterday, I was trying to install it. But also saw how many people started complaining about attacks and hack attempts. This opens doors to new business ideas to patch the blind spots.

Agents with full shell + file access hit scale issues fast when permissions and secrets are too coarse, and chat ingress gets probed as soon as it is public.

Best practice is capability based allowlists enforced by a policy engine like OPA, plus sandboxed execution (namespaces seccomp or gVisor) and append only audit logs per action.

How do you authenticate each chat channel and map users to scoped capabilities, and is per tool trace replay or human approval on the roadmap?

As a heavy power user of Poke for proactive, messaging-native assistance on top of my email and calendar, I’m curious: what are some workflows where you’ve seen Clawdbot actually outperform Poke in the real world.

This is what people have been waiting for: an open-source agent that can turn ideas into actionable plans and execution. It’s quite similar to Minara, which we launched yesterday. But we’re particularly focused on closing the loop from analysis to decision to on-chain execution in digital finance.