Docs

Changelog

Where every release of the engine, the SDKs, the MCP package, the skills and Sypnia Cloud will be listed, how an entry is written, and what the version numbers promise.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Releases
  2. How this page is kept
  3. What an entry looks like
  4. What the version numbers promise
  5. Engine and Cloud
  6. Follow changes

This page is for anyone who upgrades Sypnia or wants to know what changed. It covers what is released as software, the open-source engine, the SDKs, @sypnia/mcp and the skills Engine, and what changes in the service, Sypnia Cloud Cloud.

Releases

No releases yet.

How this page is kept

  • One entry per release, newest first. A release that changed nothing you can see still gets a line.
  • Written for the person upgrading, in plain words: what changed for you, not what changed in the code.
  • The same day as the release. A release without its entry is not finished.
  • Never rewritten. A mistake in an entry is corrected with a visible note, not by editing history.

Each component has its own version and its own entries:

ComponentVersion is seen in
The engine and the Consolesypnia version, and the Sypnia-Version header of every API answer
@sypnia/browser, @sypnia/node, @sypnia/nextThe package version in your package.json
@sypnia/mcpThe package version
The agent skillsThe plugin’s version
Sypnia CloudEntries are dated. The service has no version of its own; it runs a released version of the engine.

What an entry looks like

Every entry uses the same headings, in this order, and leaves out the ones that are empty:

HeadingHolds
To do when upgradingAnything the upgrade asks of you. Most releases have none. Always first, so nobody misses it.
AddedNew things.
ChangedThings that behave differently.
FixedBugs.
SecurityFixes for security problems, with how serious each is and which versions it affects.
DeprecatedThings that still work and will be removed in the next major version.
RemovedThings that are gone. Only in a major version.

An entry, as it will look. The version and the two fixes are an illustration, not a real release:

Markdown
## Engine 1.0.1 — <date>

### To do when upgrading
Nothing. Run `sypnia migrate`, then replace the engine.

### Fixed
- A session that crossed midnight was counted on both days in the daily numbers.
- `sypnia doctor` reported the storage check as failed on a bucket with a prefix.

When something on the Planned page ships, its entry says so and the item leaves that page.

What the version numbers promise

Versions are three numbers, major.minor.patch.

A change inMeans
Patch, 1.0.0 to 1.0.1Fixes only. Safe to take at once.
Minor, 1.0 to 1.1New things. Nothing you use stops working.
Major, 1 to 2Something was removed or changed in a way that needs your attention. Announced here in advance.

Inside version 1, these only ever add:

WhatThe promiseWhere it is written
The HTTP API under /v1New endpoints, new optional parameters, new fields and new values in answers. A breaking change would be /v2, with /v1 kept working for at least 12 months.Errors, limits, pagination
The event schemaNew event types and new fields. The engine keeps fields it does not know, so a newer SDK works with an older engine.Event schema
The engine’s settingsNew settings with defaults. A setting the engine does not know is a warning in sypnia doctor, never a failure to start, so an old setting does not stop an upgrade.Configuration reference
The databaseMigrations only add. An older engine works against a newer schema, so you can go back.Upgrades
The MCP toolsNew tools and new fields in results.Tools reference

Engine and Cloud

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Who upgradesYou, when you choose. See Upgrades, backups, retention.We do. You do nothing.
What you read hereEach engine release, and what to do when upgrading.Dated entries for changes in the app, the plans and the service.
SDKsYou choose when to update the package in your app.The same: the SDK is in your app, not in our service.

Follow changes

Until the repositories open, this page is the place. Afterwards, each repository’s releases carry the same entries, and you can watch a repository to be told of new ones.

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