04 / Automation / self-hosting
A remote gateway for the AI tools I already use
I built a Node.js service that lets me reach several command-line assistants through Telegram or email while keeping history, memory, and repository access in one place.
Starting point
Where it started
Useful CLI assistants were tied to a workstation and split across separate interfaces, histories, and repository contexts.
What I did
What I worked on
- Built command parsing and routing for three CLI-based assistants.
- Added Telegram webhooks, email polling and replies, per-channel history, and shared memory.
- Integrated controlled repository operations and sender allow-listing.
- Separated credentials from source and documented deployment, service management, and failure modes.
Result
What changed
One remote interface can dispatch work to multiple assistants while preserving useful context and keeping the operational boundary visible.
What I learned
What I took from it
- Remote convenience makes narrow authorization more important.
- Memory needs limits, compaction, and explicit ownership.
- Operational documentation is part of the feature.
Next case study / 05