npx dashclaw up, npx dashclaw install openclaw, npx dashclaw install telegram: my agent now asks my phone before doing anything destructive

I run long unattended sessions and the thing that always scared me was the one bad tool call while I'm not looking. Force push over main, rm -rf the wrong dir, agent reading .env. So I built DashClaw, an open source approval layer that sits between the agent deciding to run a tool and the tool actually running. It parses the actual bash command, git diff just runs, git push origin main freezes until I tap approve. Fail closed, and everything lands in a decision ledger so I can see what it tried while I was gone. The three commands in the title are the whole setup: the server (no account, mints your key), the gateway plugin (wizard asks for url, key and an agent id), and the telegram bridge (make a bot with BotFather, it finds your chat id, registers the webhook and fires a test approval at your phone). Approvals show up in telegram with Approve and Reject buttons, one tap and the agent unfreezes. Needs your instance reachable from the internet, mine's the free vercel deploy. Same policies cover my claude code sessions too. Honest lesson: my first policy pack fired an approval every ten seconds and I turned the whole thing off for 18 days, so the default is now catastrophe only. Real catches so far: an rm -rf, a force push, a DROP TABLE, and an agent going for .env. MIT, been running it on my own agents for months. What do you all do about this today, just vibes? https://preview.redd.it/tvlkz92qbdjh1.png?width=379&format=png&auto=webp&s=0cc7dcec1cd90dff644b29aa60bc97f74f04b3fe