CloudZero Desktop Agent 0.2.3

0.2.3 (2026-07-09)

Release 0.2.3 adds a one-click diagnostics bundle, a visible install and upgrade history, and a collector that records when and why it stops capturing usage, and clearer handling of settings managed by MDM.

New Features

• Collect Diagnostics: A new action gathers the app's logs, a snapshot of its local usage database, the install and upgrade history, and any collector crash reports into a single archive you can hand to CloudZero support. This replaces manually hunting for scattered log files when troubleshooting.
• Install and upgrade history: The app now keeps a visible record of when it was installed, upgraded, and restarted, so support can understand a machine's history at a glance.
• Attributable collector downtime: When the collector stops capturing usage, the app now records the reason — a normal quit, a logout, an app update, machine sleep, or a crash — along with periods where traffic passed through uninspected. Gaps in usage data are now explainable rather than mysterious.

Improvements

• More accurate usage attribution across restarts: Usage is now attributed to the correct identity even when the collector restarts mid-session, and requests interrupted before they complete still leave a record with whatever usage was observed. Events captured before an identity is known are labeled as such instead of being dropped.
• API key changes apply without a relaunch: Changing your CloudZero API key now takes effect immediately — the app no longer needs to be restarted for the new key to be used.
• Actionable refresh errors: When a usage refresh fails, the menu bar popover now offers a clear way to retry instead of only showing an error.
• Structured diagnostics logging: The app and collector now emit logs in a consistent structured format, which makes the new diagnostics bundle far more useful when working with support.
• Cleaner uninstall: Removing the app or its certificate now also clears the certificate-trust environment variables it had set, leaving no stale trust configuration behind.

For IT admins

• All managed settings render as managed: On machines managed by MDM, settings your administrator controls — including update-check behavior and the context-enhancement toggle — now clearly appear locked rather than editable. No configuration changes are required; this only affects how already-managed keys are displayed.
• Deployment profiles: Added example deployment configuration profiles and refreshed the MDM setup documentation.