Docs

Limits

Every limit of the agent: analyses a day, analyses per problem, pull requests a month on Sypnia Cloud, sizes, timeouts, and what happens at each limit.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Analyses
  2. Pull requests
  3. Sizes
  4. Time
  5. Weekly suggestions
  6. Change the limits

Engine Cloud The agent has limits so that a bad day cannot turn into a large bill, yours or ours. At every limit Sypnia says so in plain sight; it never analyses less quietly.

Analyses

LimitSelf-hosted engineSypnia Cloud
Analyses a day, per project100 by default. Yours to set with SYPNIA_AI_MAX_ANALYSES_PER_DAY; 0 is no limitFree 20 · Builder 100 · Team 500
Analyses a day, per problem3 by default (SYPNIA_AI_MAX_ANALYSES_PER_PROBLEM_PER_DAY)3
Asking by API (POST …/analyze)10 a minute per token10 a minute per token

A day is a calendar day in UTC. Every run counts: the first analysis of a problem, a new one because it grew or came back, and one you asked for.

At the daily limit, a new problem gets analysis.status limit_reached. It keeps its technical title, still alerts, and its prompt carries the evidence. The next day, problems that are still open and were skipped are analysed first, those that hit the most people first. An usage.limit alert is created at 80 % and at 100 %.

GET /v1/usage returns analyses.used_today and analyses.limit_per_day.

Pull requests Cloud

PlanPull requests Sypnia opens a month
Free5
Builder50
Team300

Counted per organization, per calendar month in UTC, when a pull request is opened. A pull request that Sypnia could not write does not count. See Pull requests. The engine has no pull requests and so no such limit.

Sizes

These are the same everywhere. They keep one analysis small, fast and cheap.

WhatLimit
Frames of your own code sent, with source lines8 frames, 5 lines on each side
Breadcrumbs sent30
Spans of the trace sent40, the failing ones and their parents first
Changed files of the release sent with their diff10 files, 20,000 characters of diff in all
The whole inputAbout 24,000 characters. Longer context is cut from the least useful end and the analysis notes it
The model’s answer2,000 tokens by default (SYPNIA_AI_MAX_OUTPUT_TOKENS)
Evidence items in an analysis1 to 6
The ready prompt12,000 characters

One analysis is therefore a few thousand tokens in and under two thousand out. What that costs depends on the model you chose; multiply by your provider’s prices.

Time

WhatLimit
One model call60 seconds by default (SYPNIA_AI_TIMEOUT_SECONDS)
RetriesTwice more, after 5 and 30 seconds. Then failed, and tried again when the problem grows
From first failure to an analysisUsually under 3 minutes: up to 2 for the problem to appear, then the model call

Weekly suggestions

WhatLimit
RunsOne a week per project and environment
Model calls in a runAt most 25: one per page with findings, the pages with most views first
Suggestions kept from a runAt most 20
Counted as analyses?No. They have their own cap, above

The suggestions that come from fixed rules have no limit and need no model.

Change the limits

On a self-hosted engine every number marked with a setting is yours to change, in the configuration reference. On Sypnia Cloud the limits are the plan’s; see Plans and limits.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close