
dev-workspace-2.0
Multi-agent Telegram orchestration system with Claude Code
Created Mar 2026
Exposing local development services to the internet is often necessary for testing webhooks or sharing progress externally. This update adds new instructions to the quickstart and user guides detailing how to set up secure tunnels. It covers using ngrok for rapid testing and Cloudflare Tunnels for a more robust, production-ready configuration, complete with example configurations and systemd service instructions for automatic startup. Developers will now have a much clearer path to securely sharing and deploying their local environments.
The ioredis package and all Redis-related connection and session storage code have been removed from the Telegram gateway. The project now relies strictly on file-based memory persistence across sessions, meaning you no longer need a running Redis server locally to spin up the Dev Workspace agent. Deleting infrastructure requirements drastically simplifies the setup. Always a win for the quickstart experience! 
The project has been reframed from a 'Telegram Agent System' to 'Dev Workspace 2.0' to better describe its real-world use case as an always-on development assistant. The updated README emphasizes features like continuing coding discussions across devices, analyzing documents on the go, and maintaining persistent project context in a tmux session. This clear new framing and updated architecture diagram make the project's purpose and capabilities much easier to grasp.
Introduced the foundational architecture for Pichu, a multi-agent Telegram orchestration system powered by Claude Code. The setup includes an Express gateway server for handling webhooks, a persistent tmux-based 'Commander' session to maintain conversation context, and support for spinning up fresh subagents to handle implementation tasks. It also features file-based memory management, file attachment support, and threading capabilities, laying the groundwork for complex, long-running agent workflows.
