Release channels (stable, beta)

Confidant currently ships on a single stable channel. Beta and pre-release channels are planned but not yet available. This article will be updated when they ship.

What stable means

Every release on the stable channel has gone through:

• Internal testing across our team's machines (Mac and Windows)
• Validation against a regression suite covering recording, transcription, note generation, encryption, and updates
• Manual smoke testing of the full user flow on at least one fresh-install machine
• Code signing and notarization for both macOS (Apple) and Windows (signing certificate)

We don't ship a stable release we wouldn't run on our own machines.

How to know what version you're on

Three places:

• About dialog — Confidant menu (Mac) → About; Help menu (Windows) → About
• Settings → Developer → Debug Info — shows version, build hash, model version, and other useful diagnostic info
• The update banner — when an update is available, both the current version and the new version are shown

Release notes

We publish release notes on the Confidant website (linked from your account). Each release notes:

• New features
• Improvements to note quality (especially when we ship a new model)
• Bug fixes
• Any breaking changes (rare; we try to avoid them)

If you want to be notified when a new release ships, opt in to release-only emails through your account settings on the website. (We don't email you for any other reason — no marketing, no newsletters.)

Future channels

We're planning two additional channels:

• Beta — pre-release builds that have passed internal testing but haven't been promoted to stable yet. Useful for users who want new features earlier and are willing to report issues. Opt-in.
• Insider — early-access builds for partners we work closely with on specific features. Invite-only.

Neither is live yet. When they are, you'll be able to opt in from Settings → Account → Release Channel (or similar). Stable will remain the default.

Rolling back

We don't currently host old .dmg or .msi installers publicly. If you specifically need to roll back to a prior version, contact support — we keep them on file and can provide a signed older build for genuine compatibility cases.

The reason we don't make this self-serve: rolling back can leave you on a version with known bugs (sometimes serious ones we've since fixed). We want to make sure rollback is the right call for your specific situation before facilitating it.