telegram-bot-management

Original：🇺🇸 English
Translated

Telegram bot management and monitoring. TRIGGERS - telegram bot, claude-orchestrator, bot status, bot restart.

6installs
Sourceterrylica/cc-skills
Added on

NPX Install

npx skill4agent add terrylica/cc-skills telegram-bot-management

Tags

Translated version includes tags in frontmatter
telegram-bot-managementbot-monitoringclaude-orchestratorbot-lifecycletroubleshooting

SKILL.md Content

View Translation Comparison →

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

bash
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

bash
bot-service.sh logs
# Or use alias
bot logs
Tails all logs:
  • Launchd logs (supervision layer)
  • Bot logs (application layer)

Restart Bot

bash
bot-service.sh restart
# Or use alias
bot restart
Rarely needed due to automatic code reload via watchexec.

Stop Bot

bash
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

Troubleshooting

IssueCauseSolution
Bot not respondingProcess crashedRun 
bot status
to check, then 
bot restart
launchd not startingService not loadedLoad with 
launchctl load
command
Logs emptyLog rotation or path issueVerify log path in launchd plist
watchexec not reloadingFile patterns not matchingCheck watchexec filter patterns
High memory usageMemory leak in bot codeRestart bot, investigate Python memory usage
Permission deniedScript not executableRun 
chmod +x bot-service.sh
Environment vars missing.env not loadedVerify environment setup in launchd plist
Multiple bot instancesPrevious instance not stoppedKill all bot processes, then restart cleanly