100 Hours Later: My Clawdbot is officially "Always ON" and "Zero-Leak" 🦾
I just finished a 100-hour engineering sprint, and I’m deleting my "AI Junk Drawer."
I realized that to make my agent truly Always ON, I had to stop relying on external bridges. I’ve now centralized everything into a single Google Cloud VM with Gemini at the heart of the system.
How I made it "Safer":
  • No Public IP: My VM is invisible to the internet. If you can't see it, you can't hack it.
  • The IAP Tunnel: I use Google’s private tunneling to "teleport" into my VM. Total security, zero exposure.
  • Unified Data: Because I’m using the Google ecosystem, my data never leaves the "Vault" to train public models.
How I made it "Always ON":
  • Gemini as the Orchestrator: Instead of me jumping between apps, I message my bot on Telegram.
  • Skill Integration: Gemini uses native APIs to perform Google Searches, edit my project files, and organize my repo directly on the VM.
I’ve minimized my tool stack to maximize my output.
We are no longer the "Integration Guy"- We're the Architect.
The engine handles the plumbing; I focus on improving it to make it a safer personal AI.
Stop "Prompting" and start "Architecting."
5
1 comment
Manoj Saharan
5
100 Hours Later: My Clawdbot is officially "Always ON" and "Zero-Leak" 🦾
AI Automation Society
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
Powered by