I wanted to fix my server from the grocery store. That’s really how this started.
My home lab was throwing errors and I couldn’t SSH in from my phone. I was standing in the produce aisle, frustrated, wishing I could just tell someone to fix it. Someone who had access to my server, understood what was wrong, and could actually do something about it.
The Weekend Hack
That weekend, I built the first version. A Telegram bot connected to Claude’s API with basic server access. The idea was simple:
- Send a message from my phone
- Claude analyzes the problem
- Claude fixes it (with my permission)
- I get a notification when it’s done
It worked. Sort of. The first version was held together with duct tape and wishful thinking.
Then It Grew
What started as a server management tool became something much bigger:
- Security layer - TOTP authentication, permission callbacks, fresh auth windows
- Session management - Persistent context, auto-backups every 10 minutes
- Multi-bot architecture - Different personalities for different purposes
- Enterprise-grade reliability - Graceful degradation, auto-recovery, comprehensive logging
I’ve used it to debug code, manage my NAS, research topics, and even help plan family trips.
What I Learned
1. AI tools should get out of your way
The best interaction is no interaction. Claudette runs in the background. I forget it exists until I need it.
2. Security matters more than features
I could have shipped faster without TOTP, without permission callbacks, without careful API key management. I’m glad I didn’t.
3. Build for yourself first
This wasn’t built for “users.” It was built for me. That clarity made every decision easier.
What’s Next
I keep adding features as I need them. Recently added:
- Dual-bot support (Claudette for technical work, Dottie as a life companion)
- Better error recovery
- Improved session persistence
Maybe I’ll open-source it someday. Maybe not. Right now, it’s mine, and that’s perfect.
Tech Stack: Python, Claude API (Sonnet 4.5), Telegram Bot API, SQLite, NAS SSH access, Docker
Status: Active development, daily use since December 2024