Drevon v0.4.16 - Built-in diagnostics and better crash visibility
If 0.4.15 was about polish, 0.4.16 is about support.
When something goes wrong in an agent workspace, the hardest part is rarely fixing the bug. It is collecting enough context to understand what actually happened. This release gives Drevon a much better way to do that without turning support into a back-and-forth of screenshots, copied logs, and "can you reproduce it again?" emails.
What's new?
Send Diagnostics from Settings
You can now send a diagnostics bundle directly from Drevon.
From Settings, Drevon can package a redacted support bundle with recent logs, runtime context, and a system snapshot, then upload it for review. If the upload cannot complete, the app falls back to saving the bundle to your Desktop so you still have something you can share.
That means when an agent misbehaves, you no longer need to dig through hidden folders or manually assemble logs. The app does the boring part for you.
Anonymous crash reports are now user-controlled
There is now a dedicated toggle for anonymous crash reporting in Settings.
If you leave it on, Drevon can send crash and failure signals that help us spot issues faster, especially the kind that are hard to reproduce on demand. If you prefer not to send them, you can turn it off.
This is a small settings change, but it matters: better visibility when you want it, control when you do not.
Better capture for failed agent starts and hangs
0.4.16 improves how Drevon records failures that used to disappear with too little context.
That includes early agent exits, auth-related startup failures, and app hang scenarios that happen before a normal error flow has time to render something useful on screen. In practical terms, this should make the frustrating "nothing happened" class of bugs much easier to understand and fix.
Faster support follow-up behind the scenes
We also tightened the backend support flow for diagnostics bundles.
Uploaded bundles are now tracked more reliably, and support can regenerate fresh secure access when needed instead of asking you to reproduce the same problem just because an old link expired.
You probably will not notice this day to day. But if you ever do need help, it shortens the path from report to resolution.
Why this update matters
This is not a flashy release. It is a reliability release.
The best developer tools do not just help when everything goes right. They help when something strange breaks on a Friday afternoon and you need a clean path to figure out why. That is what 0.4.16 is for.
Drevon should feel like a serious workspace for running agents, not a black box. This update moves it closer to that standard.