Drevon v0.4.17 - Fixed: hangs and authentication loops on large projects
0.4.17 is a focused stability release. Two bugs, one shared root cause, fully fixed.
If you have ever opened a large project in Drevon and seen the app go silent — no output, no error, just a frozen UI — this update is for you. Same if you have hit the re-authenticate loop where Claude asks you to log in again, you do, and then it immediately asks again.
What was happening
When you open a project in Drevon, the app watches for file changes so the agent can stay in sync with your codebase. On large projects — particularly those with thousands of files — the previous version was accidentally setting up an individual file watcher for every single file in the directory tree. A project with 15,000 files would create 15,000 watchers.
That is a lot of overhead, and on some machines it pushed the app to its resource limits. When that happened, the system could not open new connections to run processes — including the ones needed to verify your Claude authentication. The auth check would fail, the app would show the re-authenticate prompt, and no matter how many times you logged in, the underlying problem remained.
The frozen UI and the auth loop were two symptoms of the same issue.
What we fixed
We replaced the file watching approach with one that uses a single efficient system-level watcher for the entire project directory. Instead of thousands of individual handles, it now uses one — regardless of how big your project is.
The result: Drevon now opens large projects without any of the overhead that was causing these failures. Agents start reliably, authentication checks pass, and the re-authenticate banner no longer appears in normal usage.
Who this affects
This mainly affected users working on projects with a large number of files — think full CMS installations, multi-plugin setups, or anything with an extensive vendor or dependency tree that was not excluded from watching. If you hit either the hang or the auth loop in recent versions, updating to 0.4.17 should resolve both.
As always, if anything feels off after updating, you can send a diagnostics bundle from Settings and we will take a look.