The main changelog route is the canonical public update feed. Features, UX updates, and operational improvements all appear there. Use the newsletter subscription path when you want release updates delivered to you, and the GitHub releases and docs when you need longer-lived historical context.

Source of truth. Do not treat this docs page as the live release feed. This page explains how to read the release story and points at the current update channels. The actual public update stream lives on the main changelog route. Open the live changelog.

Recent product themes

These entries summarize the recent direction of the product so you can see the kinds of changes that are being shipped without reading every release note in full first.

May 2026

Latest. Recent changes grouped into one release window so you can scan the major surface-area shifts quickly.

• AI tool detail pages rebuilt around what Versalist users actually need. The Versalist-native block — challenge fit, eval score, real run counts, community prompts — is now the prominent section. Internal vocabulary like 'Agent manifest', 'Trajectories', 'Manifest status', 'Field provenance', provider capability tiers, and D0-D4 integration depth no longer surfaces on public pages.
• Agent Training Stack docs went live — the full loop from challenge to rollout to judge to reward to skill update, in one place instead of scattered across READMEs.
• Integrations docs now make it explicit what's live (bring your own provider keys) versus what's still on the roadmap (custom model endpoints, custom compute) — so the directory stops reading like a list of partners.

April 2026

Recent. Recent changes grouped into one release window so you can scan the major surface-area shifts quickly.

• Self-improving skills shipped. Skills now run against real rollouts, watch how they did, and propose their own changes. Improvement is measured against evaluations, not asserted by the author.

January 2026

Recent. Recent changes grouped into one release window so you can scan the major surface-area shifts quickly.

• Plan upgrades no longer fail at checkout.
• AI provider setup reordered so the providers people actually use show up first.

December 2025

Recent. Recent changes grouped into one release window so you can scan the major surface-area shifts quickly.

• Evaluations launched. See how a specific model performs on a specific challenge before you commit to it.
• AI credits are now buyable through Stripe — top up when you need to, no plan upgrade required.
• Pulse shipped: short daily challenges that compound into real skill over weeks.
• Any challenge can now be exported as markdown to drop into your own projects.
• New prompt workspace with full conversation history and one-click message copy.

What the changelog is for

The changelog matters because it tells you what changed in the product contract: new surfaces, workflow refinements, billing changes, challenge-system additions, or fixes that alter how a route should be used.

New surfaces and modules

Big route additions like Pulse, Evaluations, or prompt-workspace changes belong in the changelog because they change how the product is navigated.

Workflow improvements

Changes to challenge export, integrations, routing, or organization should be visible because they affect operator behavior.

Operational fixes

Bug fixes matter when they change whether billing, auth, or provider setup behaves reliably enough for normal use.

Where to follow updates

The right release channel depends on how closely you follow the product. Use the public changelog for regular review, and use the docs or GitHub releases when you need supporting historical context.

Public changelog route

Best for browsing the actual change stream in the product itself. Open /changelog.

Newsletter subscription

Useful when you want updates delivered instead of remembering to check the changelog manually. Open the changelog subscription flow.

GitHub releases

Best for longer-term historical context or when you want to inspect older release notes outside the site. Open GitHub releases.

How to interpret a release

Read a release note by asking what changed for the operator: did a new route appear, did a workflow simplify, did a billing or auth assumption move, or did a challenge or tool surface become more capable? That framing makes the changelog far more useful than reading it as generic marketing copy.