Reference
Changelog
What shipped and when. The full release log lives on the Updates page; this is the map to it.
Conifer keeps one changelog, and it is not in these docs. The canonical record of every release lives on the Updates page, newest first, built from shipped commits and not from a roadmap. A log copied onto two surfaces drifts, and a drifted log lies, so it stays in one place. This page covers how that log is organized, how to read your installed version against it, and what to do when a version number shows up in an error.
Where the log lives
Open Updates. It is the single surface for every release, across the desktop app, the engine, the model catalog, and the platform. Nothing speculative lands there: a thing that has not shipped gets no entry, so there is no “coming soon” lane.
The app updates itself in place. The macOS build is signed and notarized by Apple, so the OS permission grants you gave Conifer survive across versions instead of resetting on each update. Install once and stay current. The changelog reads as a record of what changed under you, not a list of downloads to chase.
Four release streams
One product, four parts, four cadences. The timeline interleaves all four in time, and the lane an entry lands in tells you the blast radius of the change.
| Lane | What ships here |
|---|---|
| Desktop & Studio | The signed app you install and the surfaces inside it: context sizing, recovery, cold starts, route disclosure, staged writes. This is the lane with version numbers and update prompts. |
| Engine | The runtime kernels and scheduling. The why-it’s-fast work, explained in Inside the engine. |
| Models | Which architectures the catalog supports and their measured numbers. Per-model specs live on the model ledger, not here. |
| Platform | Fleet governance, the connector pack, and the metered gateway: the parts a team needs to run Conifer on many machines. |
A new model family in the catalog is a Models entry; the engine work that lets it run is an Engine entry. Same release, two lanes, because they answer different questions.
Reading versions and dates
The Desktop lane uses semantic versions like v1.2.5. The patch digit moves for a fix or a small change, the middle digit for a feature, and a date sits beside every version so you can place it in time. The live number on Updates is the source of truth for what the latest build is, since that page tracks the releases and a sentence here would age past it.
The app’s about surface shows the version you run. Behind the latest? The in-place updater catches you up on the next launch. The Engine, Models, and Platform lanes carry no user-facing version of their own; their changes ride into the app build that bundles them, so the Desktop version is the one number you ever quote.
Related reference
The changelog says what moved. The rest of this section says what to do with a given build.
- Troubleshooting
- Symptom to cause to fix when something breaks, including the version you read off the about surface.
- Performance & tuning
- The levers that move tokens per second once a build is installed and running.
- Glossary
- One definition per term, for the runtime words a release note assumes you already know.
For the running list of what shipped and when, go straight to Updates. Everything else here points back to it.