Update button: confirm before restarting when background agents are running
Status Fixed / completed
Maintainer reply None cached
Activity 0 comments · opened Aug 5, 2026 · closed Aug 25, 2026
What happened
In the Windows desktop app, the update button sits in the bottom-left corner, large and directly above the account name. I clicked it by accident while reaching for my account — and the app restarted immediately, with no confirmation.
That restart killed four running background agents mid-write. Their uncommitted file edits survived, but their in-flight state (watchers, long test runs, half-finished verification passes) died with the process, and each agent had to be manually resumed and re-oriented. This was the third restart-and-resume cycle of the day for the same agents (the earlier ones were a usage-limit reset plus a deliberate update), so the cost of one accidental click was very tangible.
Requests
- Confirm before restarting for an update when background agents or tasks are active. Even a simple dialog — "4 background agents are running; update now anyway?" — would have prevented this entirely. Ideally the update would wait for agents to finish or offer to defer.
- Reconsider the button's size and placement. A large, primary-styled update button immediately adjacent to the account name in the bottom-left invites misclicks. A smaller affordance, or one placed away from other frequently-clicked targets, would help.
Environment
- Claude desktop app on Windows 11 Pro (10.0.26200)
- Session with multiple long-running background agents at the time of the click