telegram-bot-management
Telegram bot production management, monitoring, and troubleshooting. Use when user mentions telegram bot, claude-orchestrator, bot status, bot restart, or bot monitoring.
When & Why to Use This Skill
The Telegram Bot Management skill is a specialized DevOps tool designed for the production-grade supervision, monitoring, and troubleshooting of Telegram-based AI agents. It provides a robust framework for managing the claude-orchestrator, ensuring high availability through launchd and watchexec supervision. This skill simplifies complex backend operations into intuitive commands, allowing users to maintain stable headless Claude Code interactions with real-time visibility into process health and system logs.
Use Cases
- Real-time Health Checks: Monitor the bot's operational status, including process IDs (PID), uptime, and memory usage to ensure the system is running within optimal parameters.
- Proactive Troubleshooting: Access and tail multi-layer logs (both application and supervision layers) to quickly identify and resolve errors or connectivity issues.
- Lifecycle Orchestration: Manage the bot's lifecycle by starting, stopping, or restarting services manually when automated code reloads are insufficient.
- Process Supervision: Oversee the full process tree and launchd status to ensure the bot remains resilient and automatically recovers from unexpected crashes in a production environment.
| name | telegram-bot-management |
|---|---|
| description | Telegram bot production management, monitoring, and troubleshooting. Use when user mentions telegram bot, claude-orchestrator, bot status, bot restart, or bot monitoring. |
Telegram Bot Management
Overview
Multi-workspace Telegram bot workflow orchestration with full supervision (launchd + watchexec). Manages the claude-orchestrator Telegram bot for headless Claude Code interactions.
When to Use This Skill
- Check bot status, restart, or troubleshoot issues
- Monitor bot health and resource usage
- View bot logs and debug problems
- Manage bot lifecycle (start/stop/restart)
Production Mode
As of v5.8.0, production mode is the only operational mode.
Bot Management Commands
Check Status
bot-service.sh status
# Or use alias
bot status
Shows:
- launchd supervision status
- watchexec process (PID, uptime, memory)
- Bot process (PID, uptime, memory)
- Full process tree
- Recent log activity
View Logs
bot-service.sh logs
# Or use alias
bot logs
Tails all logs:
- Launchd logs (supervision layer)
- Bot logs (application layer)
Restart Bot
bot-service.sh restart
# Or use alias
bot restart
Rarely needed due to automatic code reload via watchexec.
Stop Bot
bot-service.sh stop
# Or use alias
bot stop
Reference Documentation
For detailed information, see:
- Operational Commands - Status, restart, logs, monitoring commands
- Troubleshooting - Common issues and diagnostic steps