Skip to content
← Back to release notes
v0.97.0 stable major release

Release v0.97.0

Jul 18, 2026

Remote into Linux machines, turn quotes into signable contracts, run backups that resume where they left off, and pull Microsoft 365 details straight into the AI assistant. A standard upgrade with no breaking changes.

Remote Management

  • Remote desktop into Linux machines. Linux remote desktop now works in the shipping agent for the first time — connect to and control a Linux device's screen just like you already can with Windows and Mac.
  • A clearer, safer elevation prompt. When you request admin rights on a Windows device, the approval dialog now appears on the secure desktop in the correct user's session, shows exactly what's being elevated (program, signer, user, command line) with a live expiry countdown, and cleans up properly.
  • Redesigned privileged-access console. The PAM console and the Windows-side elevation and session screens have been reworked, along with fixes to how consent is shown during a remote session.

Quotes & Contracts

  • Turn a quote into a signable contract. Build reusable, versioned contract templates, drop contract blocks and a PDF cover page into a quote, and fill in variables that must be resolved before you can send.
  • A permanent record of what was signed. When a customer accepts, Breeze snapshots the exact executed document and links it to the billing contract, so you always have the version they agreed to.
  • A more real-world send experience. Improved composer, MSP branding, and a more polished customer portal for reviewing and accepting.

Backup & Recovery

  • Incremental backups. Back up only what changed since the last run, instead of a full copy every time.
  • Backups that survive interruptions. Jobs now checkpoint and resume after a restart or VSS hiccup instead of starting over, and a dropped result no longer leaves a job stuck showing 'running' forever.
  • Better visibility into running jobs. See live progress (files and bytes), and stalled or orphaned jobs are automatically detected and marked failed instead of hanging.

Microsoft 365

  • Ask the AI assistant about Microsoft 365. A set of read-only Microsoft 365 lookups is now available to the in-app assistant and Breeze MCP — pull tenant details on demand, with no changes to what your connection can do.

Platform & Organization

  • A clearer organization switcher. 'All organizations' is now a pinned, distinct option at the top with type-ahead search, and each page is explicit about whether it's acting on one org or your whole fleet.
  • A partner data export API. A new authenticated API lets approved integrations pull a partner's organizations, devices, sites, configuration, assignments, and backup metadata, with full and incremental syncs.

Version 0.97.0 broadens what you can reach and manage — and turns quotes into real, signable contracts.

The headline is Linux remote desktop: it now works in the shipping agent for the first time, so you can connect to and control a Linux machine’s screen the same way you already do with Windows and Mac. Alongside it, privileged access on Windows gets safer and clearer — the elevation prompt now appears on the secure desktop in the correct user’s session, spells out exactly what’s being elevated with a live expiry countdown, and the whole PAM console has been redesigned.

On the business side, quotes become contracts: build versioned contract templates, drop them into a quote with a PDF cover page and fill-in variables, and when the customer accepts, Breeze snapshots the exact executed document and links it to the billing contract. Backups get incremental runs plus checkpoint-and-resume so an interrupted job picks up where it left off instead of starting over, with live progress and automatic detection of stalled jobs. The AI assistant also gains read-only Microsoft 365 lookups, and there’s a new authenticated partner data export API for approved integrations.

Self-hosting note: this is a standard upgrade — 33 idempotent database migrations that apply automatically, with no large data rewrites or blocking backfills, and no breaking changes. There is one new required setting this release: a dedicated PARTNER_API_CURSOR_SIGNING_KEY (at least 32 bytes of random material, base64-encoded, and different from your JWT secret) — the API will not start in production without it. As always, review the GitHub release notes before updating.