An AI coding agent in Telegram
Message @SinatraDevBot with what you want done. Sinatra opens a topic in your chat with the bot and works there: a question gets an answer, a vague request gets questions back, and a change to the code comes back as a pull request on GitHub.
A message starts a task
Send your request in the main chat with the bot. Each request there is a new task. Sinatra opens a topic for it, named after the task, and posts a Started notice in the main chat that names the topic and links to the task's page in the dashboard. You can also open a topic yourself and send the request in it; Sinatra renames the topic after the task and works there, without a Started notice.
It reacts with eyes when it picks up a request or a reply, and clears the reaction when the agent hands back or the message is dropped. Telegram's Start button sends /start, which gets a one-line welcome and starts no task.
Sinatra reads the text of your messages and the captions on media. It can't read photos, voice notes or files. The agent is told when a message carried one, so describe what's in it.
Telling it which repository
A Telegram message doesn't come with a repository. Add repo: owner/name to your message and it uses that one, as long as it's connected to the workspace. A workspace with exactly one repository that isn't empty needs nothing. Otherwise the agent picks from the repositories you've connected when it needs code, based on what you asked, so name the repository when two could fit. A question that needs no code is answered without checking anything out, and until a repository is chosen the dashboard shows Repository not chosen yet.
What the topic shows
Each agent gets one status message in the task's topic, edited in place. It shows the task's name, then Working…, Waiting for a free agent slot, Waiting for you, Done, Stopped or Failed, and a link to each pull request the task opened. Failed carries the reason when it's one you can act on. While the status reads Working…, it has a Stop button and the topic shows Sinatra typing. A task waiting because the workspace is at its agents-at-a-time limit reads Waiting for a free agent slot, with a Stop button that takes it out of line.
The agent's answer, question or plan arrives as messages in the topic. After it opens a pull request the status reads Waiting for you; Done means the task has finished, for example after its pull request merged. When a later agent starts, Sinatra posts a new status message below your latest message and deletes the old one. Telegram doesn't let a bot delete a message older than 48 hours, so an older status message stays where it was.
Replying and stopping
Send a message in the task's topic to continue: a follow-up, an answer, or the go-ahead on a plan. In the main chat, a Telegram reply to a task's Started notice continues that task too. A message in the main chat that isn't a reply starts a new task.
A message sent while the agent is running doesn't reach it. This is different from Slack, Linear and GitHub. Sinatra replies that it will pick the message up, and the message starts the next agent once the running one hands back. Once there is a pull request, leave code feedback on the pull request, where Sinatra picks it up as review rework.
To stop, press Stop on the status message or send stop on its own in the topic. Stopping keeps the task, so a new message in the topic picks it back up. Messages you sent during the run you stopped are dropped, and Sinatra quotes the start of each one so you can resend what you still need. You can also stop a Telegram task from the dashboard, with sinatra stop in the CLI, or through the MCP server or the HTTP API.
What it doesn't do in Telegram
There are no groups; Sinatra works in direct messages only. It can't read photos, voice notes or files. There is no restart: restart in a topic is an ordinary message to the agent, and a Telegram task's page in the dashboard has no Restart button, so to start over you send a new request in the main chat. And a message sent while the agent works waits for the next agent instead of steering the running one.
A few other agents reach Telegram differently. Claude Code's Channels, a research preview, lets you message a Claude Code session already open on your own machine, and Kiro Crew's Telegram interface reaches Kiro CLI agents on hardware you control. If you want the agent running on your own computer, look at those. The comparison pages go through where each one starts work.
It can be wrong
Sinatra is an AI agent, and its answers and code can be wrong. Read a reply in the topic the way you would read a new teammate's first guess, check it before you act on it, and review every pull request before you merge. Sinatra's workflow doesn't merge or deploy; you do.
Which workspace your requests go to
A Telegram message doesn't name a workspace, so your link decides. If you link from a workspace's settings, new requests go there. If you belong to one workspace with Telegram on, they go there. If you belong to several, choose one under New requests go to in Settings, Linked accounts. When a request has nowhere to go, the bot starts nothing and replies with the reason. A task's topic stays with its workspace, so switching where new requests go doesn't cut you off from older topics.
An owner or admin can turn Telegram off for a workspace from the Telegram card in Settings, Integrations. With it off, messages from members start nothing there, and replies and Stop presses in its topics are refused. Tasks already running keep running and still post to their topics, so stop them from the dashboard if you need to.
What it can see
Sinatra reads the messages you send the bot, in the main chat and in task topics. We keep the webhook payloads Telegram sends us, which include message text. Unlinking your Telegram account in Settings, Linked accounts stops messages from that account acting as you. How Sinatra handles what it reads, and what it never does with your code, is in the privacy policy and on the security page.
Setting it up
Sign in at app.sinatra.dev, install the GitHub App on the repositories Sinatra can work in, and add a Claude, ChatGPT or Cursor subscription or an API key. A Telegram task needs model access like any other task. The quickstart walks through it.
In Settings, Linked accounts, select Link Telegram and sign in with Telegram. A Sinatra account links one Telegram account, and a Telegram account can be linked to only one Sinatra account. If you message the bot first, it replies with a link to do this, and your message doesn't run, so send it again once you're linked.
Use the Open @SinatraDevBot button on the same row, or go to t.me/SinatraDevBot.
Each request gets its own topic. The full setup, including every reply the bot can send when it can't take a request, is in the Telegram docs.
What it costs
Telegram is on every plan, Free included. Free is 1 agent at a time, plus 1 waiting, with no daily limit and no card. Pro is $20 a month for the whole workspace: 3 agents at a time, plus 10 waiting, any number of people. A Telegram task counts against the same limit as a Linear ticket or a Slack thread, and waits when the limit is reached. Bring your own Claude, ChatGPT or Cursor subscription, or an API key. Sinatra never bills for model usage. That's between you and your provider.
Common questions
How do I start using Sinatra in Telegram?
Sign in at app.sinatra.dev, open Settings, then Linked accounts, select Link Telegram and sign in with Telegram. Then message @SinatraDevBot. Telegram is on in every workspace unless an owner or admin turns it off, so there is nothing for an admin to connect. Linking doesn't grant access on its own: you still need to be a member of a workspace that has Telegram on.
Can I add the bot to a group?
No. Sinatra works in direct messages only. If someone adds the bot to a group, it posts that it works in direct messages only and leaves.
Does a message I send while it's working reach the agent?
No. Sinatra replies in the topic that it will pick the message up once the running agent finishes, and the message starts the next agent when the running one hands back. If you press Stop, the waiting messages are dropped, and Sinatra posts one message quoting the start of each so you can send again the ones you still need.
Which repository does it work in?
Put repo: owner/name in your message and it uses that repository, as long as it's connected to the workspace. If the workspace has exactly one repository and it isn't empty, it uses that one. Otherwise the agent picks from your connected repositories based on what you asked, so name the repository when it could be ambiguous. A question that needs no code is answered without checking anything out.
Is Telegram on the free plan?
Yes. Telegram is on every plan, including Free: 1 agent at a time, plus 1 waiting, no daily limit, no card. A Telegram task counts against the same limit as tasks from Linear, GitHub and Slack. Bring your own Claude, ChatGPT or Cursor subscription, or an API key. Sinatra never bills for model usage. That's between you and your provider.
The same tasks start from a Linear assignment, the Sinatra label on a GitHub issue, a Slack mention, an MCP client or the CLI and API. Questions about the Telegram bot go to contact@sinatra.dev, or see Support.