A personal development workspace that you can control from anywhere via Telegram. Powered by Claude Code with persistent memory and intelligent task orchestration.
Dev Workspace is your always-on development assistant that lives in a tmux session and responds to Telegram messages. It remembers your project context, preferences, and coding standards - so you can continue development conversations across sessions and devices.
Use cases:
- Continue coding discussions while away from your desk
- Review and analyze documents/images on the go
- Track project status and blockers
- Delegate implementation tasks to AI subagents
- Maintain persistent context across development sessions
┌─────────────────────────────────────────────────────────────┐
│ Dev Workspace 2.0 │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────┐ ┌─────────────┐ ┌──────────────┐ │
│ │ Telegram │─────►│ Gateway │─────►│ Pichu │ │
│ │ (any │◄─────│ :3100 │◄─────│ (persistent │ │
│ │ device) │ │ /webhook │ │ session) │ │
│ └──────────┘ │ /reply │ └──────┬───────┘ │
│ │ /send-file │ │ │
│ └─────────────┘ │ Task │
│ │ tool │
│ ┌─────────────┐ ▼ │
│ │ State │ ┌──────────────┐ │
│ │ /memory │ │ Subagents │ │
│ │ /files │ │ (fresh, │ │
│ │ /sessions │ │ isolated) │ │
│ └─────────────┘ └──────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
# Clone the repository
git clone https://github.com/jeffwweee/devspace.git
cd devspace
# Install dependencies
npm install
# Configure environment
cp .env.example .env
# Edit .env with your Telegram bot token
# Start the gateway
npm run gateway
# Start the orchestrator session
tmux new -s cc-pichu
claude
# Then type: /commanderFor detailed setup instructions, see the Quick Start Guide.
| Feature | Description |
|---|---|
| Persistent Memory | Project status, preferences, and knowledge persist across sessions |
| Remote Access | Control your dev workspace from any device via Telegram |
| File Analysis | Send images and documents for AI-powered analysis |
| File Delivery | Receive generated files as Telegram attachments |
| Threaded Replies | Messages can be threaded for context |
| Fresh Subagents | Implementation tasks run in isolated processes |
| Slash Commands | /status, /stop, /clear, /compact |
| Superpowers Workflow | Brainstorm → Plan → Delegate → Review → Complete |
Express server handling Telegram integration:
/webhook/:botId- Receives messages, injects to tmux/reply- Sends messages to Telegram/send-file- Sends file attachments/register/:botId- Registers webhook and commands
The Pichu orchestrator skill that:
- Receives messages via tmux injection
- Parses message metadata and file attachments
- Delegates implementation to fresh subagents
- Maintains memory files
File-based persistence:
memory/- Project status, preferences, coding standards, knowledgefiles/- Downloaded files from Telegramsessions/- Per-chat session state
| Variable | Default | Description |
|---|---|---|
PORT |
3100 |
Gateway port |
TMUX_SESSION |
cc-pichu:0.0 |
tmux target |
TELEGRAM_BOT_TOKEN_PICHU |
- | Your Telegram bot token |
WEBHOOK_URL |
- | Public URL for webhook (e.g., Cloudflare tunnel) |
Dev Workspace uses a structured development workflow:
| Skill | Purpose |
|---|---|
brainstorming |
Explore requirements before implementation |
writing-plans |
Create bite-sized implementation tasks |
subagent-driven-development |
Execute with fresh subagents + reviews |
verification-before-completion |
Verify before claiming completion |
Workflow: Brainstorm → Plan → Delegate → Review → Complete
- Quick Start Guide - Get running in ~5 minutes
- User Guide - Full documentation
- Plans Directory - Design docs and implementation plans
- Node.js 18+
- tmux
- Claude Code CLI
- Telegram Bot Token
MIT