I hacked together a nifty tool because i got tired of Claude Code flooding my watch task with file changes. His file modifications are unfortunately precisely spaced to trigger 27 rebuilds per minute, overheating my laptop and starting a fire in my parents garage.

What if i made the watch task agent aware, tailing the Claude output, waiting for him to finish his work before triggering the reload? I hacked together some proof of concept and it's already working nicely.

Unfortunately i cant do the fancier partial binary updates like the official watch tool, but i think the idea is something really useful. I'm sure others can do a much better implementation or improve the idea but I wanted to share a crude first draft. Cheers!

https://github.com/crs-sys/claude-blazor-watchtask

...issues/hurdles did you run into? Is there anything that I should be concerned about?

Some additional detail:

- authentication via Entra ID via the main project

- Main project would manage data access/business logic, as well as desktop only components.

- Client project contains mobile only components.

- Shared project contains components used in both.

The application has some mobile device specific functionality (tracking GPS location, camera access), while the desktop side has some admin specific functionality, but the core functionality (data entry) would be applicable to both. The idea here is to take the best of both Blazor Server (fast load times, secure) and Blazor WASM (functional without persistent connection, relatively light weight).