Skip to main content
Wizzo

Wizzo v0.51.0 Release Notes

Released Jun 9, 2026Public Beta
Share on XShare on LinkedInShare by email

Highlights

  • Selected `v0.51.0` as the First-Win Follow-Through Beta, focused on turning one source-backed recommendation into one visible completed win across chat, Today/Journey, voice, personalization, and onboarding.
  • Improved accepted first-win recommendations so source-backed chat suggestions keep Trial-aware routing, useful labels, time estimates, and show/accept/create telemetry instead of landing as generic quests.
  • Kept accepted first-win recommendation quests visible in Today/Journey as the primary next-win path when no overdue or due-today work needs attention.
  • Aligned Journey voice follow-up quests with the first-win contract so spoken check-ins create classified AI recommendations with useful labels, theme decisions, and funnel telemetry.
  • Extended Today/Journey first-win follow-through telemetry so started, snoozed, completed, and chat-handoff actions emit privacy-safe funnel evidence without raw quest title or notes.
  • Added a Journey first-win dismiss path so users can remove a recommended next-win card from the primary Today plan without archiving the underlying Trial quest, with dismissed funnel telemetry.
  • Reworked quiet Journey states so first-run and caught-up users can ask Wizzo for one Trial-aware first-win recommendation instead of falling back to generic planning or achievement review.
  • Added the `v0.51.0` first-win release readiness gate with `pnpm validate:v051-readiness` so source-backed recommendations, Trial-aware routing, Today/Journey visibility, voice follow-through, privacy-safe funnel telemetry, quiet-state guidance, and hosted release evidence are validated before tagging.

Fixes

  • Fixed repeated Today/Journey and voice check-in chat handoffs so a second handoff with the same prompt text still reloads when it is a distinct new action.
  • Clarified MCP connector setup states so missing provider endpoints or webhook secrets show as setup-required instead of operational failures in settings and admin rollout evidence.

Known issues

  • _None yet_
Back to releases