Features
Everything TeleCoder does, by area. Commands are listed in full in Commands.
The agent
Section titled “The agent”- The real Claude Code agent with its tools (Bash, Read, Write, Edit, Glob, Grep, web search and the rest), running on your machine as your user
- Two transports, switched with
/method: the Claude Agent SDK (the default), or the realclaudeCLI driven in a pseudo-terminal (PTY), where a project’sCLAUDE.md, settings, skills and slash commands work as in your terminal and its permission dialogs arrive as buttons - Streaming replies: the answer shows while Claude writes it, on both transports
- Model and effort pickers (
/model,/effort), and plan, explore and loop modes /modesets how much Claude asks before acting, from manual to bypass/compact,/contextand/cost, as in the CLI, and/projectcommandslists every slash command a project has/commands <words>searches the bot’s commands by name and description, where Telegram’s own/menu only matches the start of a name, and a mistyped command gets the likely ones as buttons instead of reaching Claude- Marketplace plugins you name in
CLAUDE_PLUGINScome along - A provider router with one-tap failover to Claude Code Router when Max throttles (Providers)
Threads and sessions
Section titled “Threads and sessions”- Each thread is its own session: forum topics in groups, and threads in private chats on a bot with Threaded Mode. A new thread is a new session, named after what it’s about
- Session resume across messages, and
/resume,/continueand/recapto get back to earlier work, including sessions started in your terminal /promptslists the prompts you sent, and branches from any of them/teleportcontinues a session in your terminal;/handoffexports it as markdown- Chats carry on by themselves after a restart
- Project-based working directories, picked with
/project - Threads and forks
/forkcopies the conversation into a new thread on a bot with threads, or a new branch on this one, or hands it to a sibling bot/spinoff <task>splits a task off into a new thread, with the context compacted around it and the task as its first prompt/treedraws the conversation’s fork tree; tap a point to carry on that branch or branch from it/deletethreaddeletes a thread and ends its session. A thread deleted by hand is noticed the first time something is sent into it, and an idle PTY session’sclaudeis ended after an hour either way- Threads and forks
Working while Claude works
Section titled “Working while Claude works”/btwasks a side question without interrupting the running task/steerstops the turn and sends a correction in its place;⚡ Interrupt & sendon a queued message does the same/latersets an idea aside, and once Claude is done the bot asks whether to send it- Messages that have to wait say so, and can be taken back or set aside
- Rapid split pastes are combined into one prompt
- Predicted next-prompt buttons under each reply (
/suggestions) - Working while Claude works
Background and scheduled work
Section titled “Background and scheduled work”- Background tasks and Monitor events relayed to Telegram as they happen
/tasksand/shellsto inspect and stop what’s running, with a background task’s output so far in PTY mode/schedulefor recurring prompts (every 5m,daily 9am, or cron)- Background and scheduled work
Claude can reach you
Section titled “Claude can reach you”- MCP tools let Claude ask with buttons or polls, send files, and (in PTY mode) schedule prompts
- Several questions at once arrive as one form: step through them, go back to change an answer, and nothing reaches Claude until you tap Submit, as in Claude Code’s own dialog
- Secrets stay out of the chat: you send a key, the bot deletes it and hands it to the
command Claude named, and a Claude token can be made on the spot with
claude setup-token - Talk naturally: Claude picks the right tool without explicit commands
Multiple bots
Section titled “Multiple bots”- Run several bots from one launcher, each with its own sessions and preferences
- Add, remove or change a bot in
instances.jsonwhile the others keep running - Create a bot for a project from Telegram with
/newbot, no BotFather chat needed, with that project as its home and the TeleCoder icon as its picture - Apply a setting everywhere with
/model sonnet all - Setup
Reliability
Section titled “Reliability”- An agent watchdog that detects silent or stuck tools, with
/cancelworking during hangs - A memory guard: a message that would start a new
claudeon a machine short of memory ends the idle claudes first, and asks before starting when that isn’t enough;/statusshows the machine’s available memory and the claudes running /syncresends a reply Telegram missed/restartbotand/updatefrom chat; the background service brings the bot back/rebuildbot idlebuilds once and restarts each bot as soon as it has nothing left to finish: no turn running, no background task or shell command out, no reply still on its way, no thread name still to update. One message keeps the tally, with buttons to restart the rest now or call it off- On an npm install,
/updateupgrades TeleCoder itself and/versionchecks for a newer release
Sharing and permissions
Section titled “Sharing and permissions”- Admins, approvers and guests, and per-group contributors and spectators
- A permission gate on every transport, a scope guard for paths, and a plain-language charter read before a guest’s message runs (Sharing a bot)
/allowand/denylet people in or out from chat, without a restart/autoapproveanswers the gate in advance for a while, for jobs made of many guarded commands
Voice and audio
Section titled “Voice and audio”- Send a voice note: it’s transcribed with Groq Whisper and fed to Claude
/transcribefor transcription on its own/ttsspeaks replies back as Telegram voice notes, through Groq Orpheus or OpenAI- Voice
Rich output
Section titled “Rich output”- Formatting sent as Telegram entities: nothing to escape, and a long reply splits anywhere without breaking its bold, links or code blocks
- A status line closing every reply: topic, project, effort, model, context use and cost,
on by default and sent silently;
/statuslineturns it off or adds your last prompts and aclaude --resumecommand - Terminal-style tool status (
/terminalui) and four verbosity tiers (/verbosity) - Claude Code’s task list as a live card
/topicsets the conversation topic shown in the status line and as the thread’s name;/botnamerenames the bot in Telegram, without a trip to BotFather- Optional Telegraph Instant View for long replies (opt-in with
TELEGRAPH_ENABLED=true; pages are public) - Inline keyboards for settings
Files and uploads
Section titled “Files and uploads”- Send photos or image documents; they’re saved under
.telecoder/uploads/in the project, a folder that keeps itself out of git /filesends you a file from the project (credential files such as.envand~/.sshare never sent)
telecoder init, a wizard that checks the bot token, learns your user ID and writes the configtelecoder service installfor a systemd user service on Linux or a LaunchAgent on macOStelecoder doctorchecks Node, theclaudeCLI and its login, and the config- Install and run and the CLI reference