Sinatra vs Augment Code
Augment's cloud agents, now shipped as Cosmos Experts with configurable triggers. Compared here on those Experts, not on the Auggie CLI or the editor extension.
Augment's cloud agents ship as Cosmos Experts: you build an Expert, give it capabilities, and attach triggers with event types and filters. It is the most configurable product on this list and the most powerful if you want agents doing things other than closing tickets. It is also the only vendor here that states a percentage markup on its own pricing page, a flat 40% fee on model usage, and it has no bring-your-own-key path and no free tier.
- Yes means the vendor's own app starts a run from the issue itself, with nothing to commit to the repo first. Sinatra's trigger is the Sinatra label that ships with the GitHub App install (`sinatraai` on the hosted app). Partial means either that a workflow file and an API-key secret have to be added per repository first, or that the mention only works on pull requests, or that starting from an issue needs a trigger or automation you configure yourself.
- Yes means assigning the ticket to the agent in Linear starts the run. Partial means the run starts some other way: an attachment link you click, or a trigger you configure yourself against Linear's webhooks. Assignment on its own does nothing.
- Yes means a documented HTTP API or MCP server starts a run on the vendor's hosted agent from a task the caller writes, so a script, a CI job, or an MCP client can hand off work and follow it to a pull request. Partial means only the vendor's CLI can start such a run, or the API only fires an automation saved ahead of time, or it is enabled for selected organizations only. Local agent sessions, and MCP servers that only read docs or tickets, don't count. Creating, labeling, or assigning an issue through a tracker's API, so that a tracker trigger or a saved automation picks it up, doesn't count either. Sinatra's MCP server takes an OAuth sign-in from Claude Code, Cursor, claude.ai or ChatGPT, or a personal access token; the HTTP API and the `sinatra` CLI take the token; and every run happens on Sinatra's hosted agent.
- Yes means a changes-requested review is enough on its own: Sinatra reworks the branch and pushes the follow-up commit with no re-trigger and no mention. Partial means the agent acts only when it is @-mentioned in the thread, or only while its original session is still open.
- Yes means your own provider API key runs the agent everywhere the product runs it. Partial means keys work on some surfaces but not the one being compared here, either because the vendor documents them as local-CLI-and-desktop only, or because it never documents them covering its cloud agent at all.
- Yes means a Claude Pro/Max or ChatGPT subscription you already pay for authenticates the run on the vendor's hosted cloud. Partial means it works only where that CLI's login already sits on the machine: your own laptop or a self-hosted backend, not a clean cloud sandbox, or that a linked subscription pays only for one provider's share of a hosted run while the vendor bills the rest.
- Yes means the vendor never charges you for model use itself: it runs on a key or subscription you pay a model provider for, or model use is included in a flat plan and capped by a rate limit or task quota rather than charged. When the vendor is itself the model provider, paying its own API rates on your own key counts as paying your provider. Partial means the vendor bills model use unless you bring your own key on the surface compared here. No means the vendor bills model use, as tokens, credits, or units, at cost or marked up, including usage past an included allowance. Sinatra runs on your own Claude or ChatGPT subscription or API key and never bills for model usage.
- Both halves have to be published: the plan price, and the rate for work past the plan. A published seat price sitting on top of an undisclosed credit, compute unit, or quota size is partial.
- Yes means the free tier states its limits as numbers. Sinatra's Free plan is 1 task at a time, plus 1 queued with no daily limit and no card, on your own subscription or API key; each request runs for up to 60 minutes, and if it needs longer Sinatra stops, keeps the changes, and picks up when you reply. Partial means a free plan exists but its limits are not published, or are published in a unit whose size isn't. No means there is no free tier, or the free tier leaves out the agent compared here.
- Yes means the vendor supplies model access and bills for or includes that usage. Sinatra requires your own workspace API key or personal subscription on every tier, including existing and paid accounts, and does not bill model tokens.
- Yes means an editor plugin or a desktop app; partial means a terminal CLI and no plugin or app of the vendor's own inside an editor. Sinatra is partial: the `sinatra` CLI, and an MCP server that Claude Code, Cursor, claude.ai, ChatGPT and other MCP clients can call, hand work to the hosted agent, which works in its own sandbox and comes back as a pull request. There is no editor extension, and the agent never runs on your machine. If you want an assistant working inside your editor, that is a real reason to pick one of these instead, and several teams run both.
- Yes means mentioning the agent in a Slack channel or thread starts a run on the vendor's hosted agent. Sinatra's Slack app is connected once per workspace by an owner or admin, on every plan: mention it in a channel and it works in that thread, posting its progress and answer there and opening a pull request when the request needs code. Follow-ups in the thread continue the task.
- Yes means you can run the agent on infrastructure you control, or the source is open. Partial means execution or inference can be pointed at your own account or your own machines while the product itself stays the vendor's and stays closed. Sinatra is hosted only; there is no self-managed build.
Competitor facts were read off each vendor's own documentation and pricing pages on September 4, 2026. The “Start a hosted run over API or MCP” row was read on October 13, 2026. Sinatra's terms reflect the current own-credential requirement.
How you start it
- Add the Sinatra label to a GitHub issue. The label ships with the GitHub App install and is named after the app (
sinatraaion the hosted one) - Assign a Linear ticket to Sinatra, or @-mention it in a comment
- Mention @Sinatra in a Slack channel; it works in that thread, and follow-ups in the thread continue the task
- Start a task from your terminal with the
sinatraCLI, from Claude Code, Cursor, claude.ai or ChatGPT over MCP, or over the HTTP API. It runs on Sinatra's hosted agent, not on your machine
- A Linear trigger configured on a Cosmos Expert, with an event type and a JSONLogic filter
- A GitHub trigger for issues, issue comments, pull requests, pushes, CI failures, or slash commands
- The Augment Slack bot
- The Auggie CLI and the Augment editor extension
auggie cloud session createin the Auggie CLI, which launches a session from an Expert (read October 13, 2026)- A custom webhook wired to one Expert's trigger, which runs that Expert's saved configuration (read October 13, 2026)
Free: 1 task at a time, plus 1 queued, no daily limit. Bring your own Claude or ChatGPT subscription, or an API key. On Free, each request runs for up to 60 minutes. If it needs longer, Sinatra stops, keeps the changes, and picks up when you reply. No card. Paid plans are one flat monthly price for the whole workspace, however many people are in it: Pro $20 (3 tasks at a time, plus 10 queued), Team $99 (10 tasks at a time, plus 25 queued), Scale $249 (25 tasks at a time, plus 100 queued). Enterprise is custom. Sinatra never bills for model usage.
Sinatra pricing →Standard $20 a month buys $20 of usage across model, context engine, and compute, with up to 50 seats; Business $100 a month buys $100 of usage; Enterprise is custom. There is no free tier. Augment's pricing page states a flat 40% fee on model usage, with no fee on compute. It is the only percentage markup on this site, and the largest of the two published fees.
Augment Code pricing page →How you start a task
Augment's model is configuration, not convention. A Linear trigger takes a webhook event type and an optional JSONLogic filter against the raw payload. Once wired, it is powerful and precise, and you can express rules no assignee field could.
The cost is that nothing works until someone builds it. There is no out-of-the-box "assign the ticket to Augment" and no label that starts a run on a fresh repository. There is an Expert someone authored and a filter someone maintains.
Sinatra takes the opposite position: a GitHub label and a Linear assignment that
work with no configuration, a CLI and MCP server that start the same task with a
personal token, and defaults that work without a .sinatrarc.
Which is better depends entirely on whether you want a platform or a teammate. If the answer is a platform, stop reading and use Augment.
What it costs, in dollars
Augment publishes something almost nobody else does, and it deserves credit for the candor even as we argue with the number: a flat 40% fee on model usage, with no fee on compute. Only one other vendor here publishes a fee on model usage at all, and Cursor's is $0.25 per million tokens on its team plans.
Fifty seats for $20 is a striking headline, and for a team running a handful of tasks a month it may well be the cheapest thing here. The 40% is what compounds. Every dollar of model work costs you $1.40, forever, scaling exactly with how much you use the product you are paying for.
Sinatra charges a flat monthly price for the whole workspace, $20 on Pro, and never bills for model usage at any volume. Your provider bills you at their published rate, or your subscription covers it and the marginal cost is zero. The free tier is 1 task at a time, plus 1 queued, with no daily limit and no card.
At small volumes Augment wins on price. At the volume where an agent is actually part of how your team works, 40% on every token is the line that matters, and it is the reason this page exists.
Where Sinatra wins
Nothing is added to model cost. Not a percentage, not a per-token fee, not a credit conversion, not a compute unit. Your provider's rate on your provider's invoice, or nothing at all on a subscription you already hold. Augment documents no bring-your-own-key path, so there is no version of it where the model bill leaves its billing relationship.
The triggers work on install, with no Expert to author and no JSONLogic filter to maintain as Linear's payloads change. There is a free tier at all, where Augment starts at $20 a month. And rework comes from a review with no mention, so you did not have to configure a trigger in advance for that event.
Where Augment wins
It is an automation platform, not one workflow. Experts with custom capabilities, triggers across GitHub, Linear, Slack, Teams, and ClickUp, scheduled automations, a feedback triager that turns Slack reports into tickets, and an analyst that reports on pull-request activity and cost. Sinatra does ticket-to-PR and nothing else.
Fifty seats for $20 a month, with $20 of usage included, is a real advantage if your usage is modest, and no amount of markup arithmetic changes it.
The context engine is what the company is known for and the part a comparison table cannot capture. Auggie CLI and the editor extension add a terminal agent and an in-editor assistant with skills, hooks, subagents, and plugins, where Sinatra's CLI only hands a task to its hosted agent and there is no editor extension. And its filters are more expressive than anything Sinatra offers: if your rule is "only P1 bugs in these three projects, and only after triage", Augment can state that and Sinatra cannot.
Looking for an Augment Code alternative?
Almost everyone who searches this has done the same arithmetic. They like the agent, then they multiplied a month of model usage by 1.4.
Sinatra's answer is the narrow one. Connect the key or subscription you already pay for, and the model half of the bill goes to your provider at their rate with nothing added, at any volume. Our charge is $20 a month for the whole workspace on Pro for the sandbox and the orchestration, and it does not move when a week gets busy: extra tickets queue rather than bill.
What you give up is the platform: no Expert builder, no Slack triager, no scheduled automation, no JSONLogic filter, no context engine. If those are why you bought Augment, the 40% is buying you something real and you should keep paying it.
Switching, or running both
They do not collide, because Augment only responds to triggers you configured. Leave your Experts pointed at whatever they already handle and add Sinatra's label and Linear assignee next to them. Judge it on an invoice rather than a table: send a month of the tickets you would have handed an Expert to Sinatra with your own credential attached, then put Augment's usage line, model plus forty percent, beside Sinatra's plan and what your provider actually charged.
Questions people ask about Augment Code and Sinatra
Does Augment charge a markup on model usage?
Yes, and it says so plainly: a flat 40% fee on model usage, with no fee on compute. Publishing that is more honest than burying it in a credit unit, and it is still 40% on top of what the model costs.
Can Augment start work from a Linear issue?
Through configuration. Cosmos Experts take a Linear trigger where you pick a webhook event type and optionally write a JSONLogic filter, which is more flexible than an assignee and also a build rather than a menu item.
Is there an Augment free tier?
No. Standard is $20 a month, buying $20 of usage across model, context engine, and compute for up to 50 seats.
What is Augment better at?
Building agents that are not ticket-to-PR: Experts with custom capabilities, triggers across GitHub, Linear, Slack, and ClickUp, scheduled automations, and an ROI analyst.
Where these facts came from
Every mark on this page comes from Augment Code's own documentation and pricing pages, not a third-party roundup: read on September 4, 2026, except the “Start a hosted run over API or MCP” row, read on October 13, 2026, as were the ways to start a run tagged with that date. Sinatra's side of this page was last updated on October 15, 2026. If something here is out of date or wrong, tell us and we will fix the page.