CloudZero Desktop Agent 0.3.3
| Version | 0.3.3 |
| Channel | beta |
| Released | 2026-08-20 |
| Platform | Macos |
| Requires | macOS 14.0+ |
| Size | 37.7 MB |
| SHA-256 | d483295bd45355afb9ef2940abf6496c12c658f7e095fd7404ef55c6a6fa01de |
Release Notes
0.3.3 (2026-08-20)
Release 0.3.3 closes defects in certificate storage, identity capture, startup supervision, and the context markers CloudZero adds to requests.
Bug Fixes
-
Context markers are stripped more reliably from assistant replies: CloudZero adds markers to a request so the spend it produces can be attributed to the right project. When a model echoed one back and closed it with the wrong tag, the whole marker block was left on screen and the turn was attributed to nothing. Known cases are fixed, including replies where the model returned unusable marker data. Reading those markers is now consistent everywhere, so what gets removed from a reply and what gets used for attribution can no longer disagree, and one malformed marker costs only its own value instead of the block around it.
-
A failed Keychain write no longer destroys the proxy certificate authority: A failure while storing the certificate authority's private key could leave the Mac without one. The key is now written in place, and a store that did not land is reported instead of trusted.
-
Identity edits are saved when you finish, not as you type: Settings → Identity saved on every keystroke, so an intermediate value became a persisted, shippable record and an inference running mid-edit could be attributed to a partial email address. Edits now commit on Return, on leaving a field, on closing the pane, and on quitting the app. Both places CloudZero records identity are written in the same operation, so they can no longer disagree about the current value.
-
CloudZero is no longer left running unsupervised after an interrupted install: If the background service was on disk but had never been registered for the current login session, CloudZero started anyway and stayed unsupervised, so it would not come back after a crash or at the next login. It now registers the service and confirms the registration took, and every path that ends unsupervised writes a log line naming why.
Improvements
- Diagnostic bundles capture monitor health from every place it is written: The app and the network extension record monitor health in separate files that can diverge, and a bundle carrying only one of them could misrepresent monitor health. Bundles now collect all of them, and record which were absent on that machine.