Quickstart
Connect GitHub, choose model access, and start your first task. Linear, Slack and Telegram are optional.
Getting Sinatra running takes a few minutes. There's nothing to deploy — sign in, connect your tools, and assign an issue, mention Sinatra in Slack, message it on Telegram, or start a task from your terminal.
1. Sign in
Go to app.sinatra.dev/signup and continue with GitHub, or enter your email to get a one-time link. The link works once and expires after 15 minutes, and a new address gets its account only when you use the link. The page it opens lets you choose a password, so next time you sign in at app.sinatra.dev with your email and password; an existing email account can set one from Forgot password?. See Signing in. If your team already has a Sinatra workspace, accept its invitation or request access. Otherwise, continue to the GitHub App installation step to create one.
2. Install the GitHub App
From the dashboard, install the Sinatra GitHub App on the organization (or personal account) whose repos you want Sinatra to work in, and pick the repositories it can access. A new installation creates a workspace for that GitHub account. In the workspace's Repos tab, enable the repositories Sinatra should work on.
On an organization, you need write access to every repository the installation covers, as an organization owner has; otherwise Sinatra doesn't connect it. To install on your personal GitHub account after signing up by email, first use Link your GitHub account on the setup page, or Link GitHub in a workspace's Settings. Not ready for GitHub yet? Skip for now sets up a workspace that answers questions and plans, and so does installing the app without picking any repositories; see Workspaces without GitHub.
Installing the app requires permission on GitHub; changing shared Sinatra configuration requires the owner or admin role. See GitHub App for requested permissions. Sinatra works on branches and opens PRs; merging stays with you.
3. Connect Linear
An owner or admin can connect the Linear workspace from the dashboard. Each teammate who delegates work from Linear, or searches and delegates Linear issues from the dashboard, MCP, CLI or API, must also join the Sinatra workspace and use Connect your Linear account in Settings → Linked accounts. Authorize the same Linear organization that the workspace uses. See Linear setup.
You can skip Linear and run on GitHub issues alone.
To work from Slack too, an owner or admin connects it from Settings → Integrations, then invites Sinatra to the channels you want to use. Sinatra matches each member's Slack account by email; anyone it can't match uses Sign in with Slack in Settings → Linked accounts. See Slack.
Telegram needs no setup from an owner: it's on in every workspace unless an owner or admin turns it off. Each person who wants it uses Link Telegram in Settings → Linked accounts, then messages @SinatraDevBot. See Telegram.
4. Add model access
Every account, including existing and paid accounts, needs its own model credentials before delegating work. Each member can connect a personal subscription in Settings → Models for their own tasks. An owner or admin can add a shared Anthropic or OpenRouter API key for authorized workspace members. A teammate's personal connection does not cover your tasks. See Models for all supported connections.
For reproducible setup, commit a .sinatrarc.json with dependency installation commands and your test command. You can also set personal agent preferences from Repos → repository.
5. Hand it an issue
Choose a small issue with a clear expected outcome. On Linear, assign it to Sinatra or @-mention Sinatra in a comment; name the target repository if it could be ambiguous. On GitHub, add the Sinatra label — sinatraai on the hosted app, provisioned on enabled repos. In Slack, mention @Sinatra in a channel with the request, adding repo: owner/name if the workspace has more than one repository. On Telegram, send the request to @SinatraDevBot, with the same repo: owner/name hint.
Or start it from your terminal: run npm i -g sinatra.dev and sinatra login, approve the CLI in the browser page it opens, then run sinatra "fix the flaky retry test" inside a checkout of the repository you want it to work on. Claude Code and Cursor can start tasks too, through Sinatra's MCP server. See CLI, MCP and API.
If the issue is vague, Sinatra may first ask questions or propose a plan in an ordinary reply. Answer on the ticket, in the Slack thread, in the task's Telegram topic, or in the task's conversation, adjust the plan, or tell it to go ahead. There is no separate approval step. During implementation it opens a draft PR, runs the configured test command after the agent finishes, and performs self-review. Check the reported results before merging. See How it works for review feedback and stopping a run.
Pricing
Free is 1 agent at a time, plus 1 waiting, with no daily limit and no card. Pro is $20 USD a month for the whole workspace: 3 agents at a time, plus 10 waiting, with as many people as you like. Team ($99) is 10 agents at a time, plus 25 waiting, and Scale ($249) is 25 agents at a time, plus 100 waiting. An agent starts each time you ask Sinatra to work and works until it hands back. Assign as many tickets as you want. Your plan sets how many agents work at once; the rest wait and start on their own as soon as one finishes. If the queue is full, Sinatra says so on the ticket instead of starting it. On Free, each agent works up to 60 minutes, then stops and saves its work; finishing it takes an upgrade. On paid plans, agents work until they're done. Sinatra never bills for model usage; your provider's charges and usage limits apply separately. See Billing for every plan, how the queue works, and Enterprise terms.