Docs

The agent

How Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.

Applies to EngineCloud At launch

View as Markdown

Engine Cloud The agent is Sypnia’s own analysis. It reads a problem and writes, in plain words, what happened, who it hit, since when, the likely cause with its evidence, and what to do. It is not your coding agent: it never touches your code. It prepares the work for the agent that does.

There is no magic in it. One model call per problem, over evidence the engine collected by fixed rules, checked afterwards against that evidence. This section says exactly what goes in, what comes out, and what happens when it does not know.

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
The analysis in plain wordsWith your own model key. Off until you set oneIncluded
The ready promptAlways. Without a model it carries the evidence and no causeAlways
Weekly suggestionsThe fixed rules always; the rest with your model keyIncluded
Pull requestsNot in the engine. Use the prompt or the MCP server with your own coding agentOpened by the Sypnia GitHub App
Which modelThe one you configureChosen by us, reached through OpenRouter
  • How the analysis works

    What triggers it, what it reads, its steps, what it writes, and how it says «not enough evidence».
  • The prompt

    The exact structure of the ready prompt, with a full example.
  • Pull requests

    Sypnia Cloud: what the pull request contains, what the GitHub App may do, and what it never does.
  • Models and what is sent

    Which model runs, how to connect yours, and every piece of data that leaves.
  • Limits

    Analyses a day, pull requests a month, sizes and timeouts.

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