The agent
How Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.
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.
| Sypnia engineOpen source, self-hosted | Sypnia CloudPaid service, with a free tier | |
|---|---|---|
| The analysis in plain words | With your own model key. Off until you set one | Included |
| The ready prompt | Always. Without a model it carries the evidence and no cause | Always |
| Weekly suggestions | The fixed rules always; the rest with your model key | Included |
| Pull requests | Not in the engine. Use the prompt or the MCP server with your own coding agent | Opened by the Sypnia GitHub App |
| Which model | The one you configure | Chosen by us, reached through OpenRouter |
- What triggers it, what it reads, its steps, what it writes, and how it says «not enough evidence».
- The exact structure of the ready prompt, with a full example.
- Sypnia Cloud: what the pull request contains, what the GitHub App may do, and what it never does.
- Which model runs, how to connect yours, and every piece of data that leaves.
- Analyses a day, pull requests a month, sizes and timeouts.