Skip to main content

Documentation Index

Fetch the complete documentation index at: https://superturtle.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

This page reflects the current implementation in:
  • super_turtle/claude-telegram-bot/src/index.ts
  • super_turtle/claude-telegram-bot/src/handlers/commands.ts

​
Registered Slash Commands

These commands are currently wired with bot.command(...) in index.ts.
Slash commandAliasesWhat it does
/newnoneResets both drivers (stopping active work), starts a fresh session overview
/stopnoneStops the active driver run and attempts to stop running SubTurtles
/statusnoneShows the same overview as /new without resetting sessions
/looplogsnoneSends the last 50 lines from the current main loop log (/tmp/claude-telegram-<token-prefix>-bot-ts.log)
/pinologsnoneShows log-level buttons (Info/Warning/Errors) for the current Pino log (/tmp/claude-telegram-<token-prefix>-bot.log.jsonl)
/usagenoneShows unified Claude + Codex quota/usage (when available)
/contextnoneShows Claude context usage for the active Claude session
/modelnoneOpens model/effort picker for the active driver
/switchnoneSwitches active driver (claude or codex)
/resumenoneUnified picker across Claude + Codex sessions, with a Continue current button and compact driver-tagged entries
/sub/subs, /subturtle, /subturtles, /turtle, /turtlesShows SubTurtle status with task/backlog summary and state/stop buttons
/cronnoneLists scheduled jobs with cancel buttons
/debugnoneShows internal diagnostics (driver/session/queue/background status)
/restartnoneRestarts the bot process via restart marker + exit

​
Stop Intents (Command-Like)

These are handled as stop intents in text handling:
  • /pause
  • /abort
  • ! (single character)
  • Natural language variants recognized by isStopIntent(...) (for example, please stop now)
When matched, the bot stops active driver work and attempts to stop running SubTurtles.

​
Notes

  • /cron does not currently have a /jobs slash alias in source.
  • Use /looplogs for raw launcher/runtime output (run-loop.sh, stdout/stderr). The legacy un-prefixed log path is still supported as a fallback.
  • Use /pinologs for structured app logs when you need level/module filtering.
  • Programmatic control-plane operations (usage/model/driver/session/restart) are documented in MCP Tools under bot_control.