Changelog

Read recent changes and find the complete product release history.

The product changelog is the release source. This page shows the four most recent release groups.

Recent changes

May 2026

  • AI tool detail pages rebuilt around what Versalist users actually need. The Versalist-native block now leads with challenge fit, eval score, real run counts, and community prompts. 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

  • 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

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

December 2025

  • 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.

Release channels

  • Product changelog contains the current public release history.
  • GitHub releases contain repository release records when available.
  • The changelog subscription sends published product updates by email.

Read a release

Check these items before you change an integration or procedure:

  • New or removed routes
  • Authentication or permission changes
  • API or CLI behavior changes
  • Billing changes
  • Challenge or evaluation contract changes
  • Known operational fixes

Documentation and release notes

Documentation describes current behavior. Release notes describe behavior changes. Use the documentation for implementation work.

Was this page helpful?