Repository navigation
OpenCode Desktop App is spending too much CPU power on animating progress indicators #34045
Description
Description
Basic conversation is running. Waiting on super-slow Opus 4.8 to think up its answer. Yet, the CPU is burning in my notebook for no good reason.
Since WebKitWebProcess is correlating in time for this kind of load, I suspect OpenCode spends a full CPU core animating a progress spinner (animated line at the top of the screen) and the shade of colors on the conversation's icon.
That's the problem with integrating a browser into a desktop app, then updating it continuously. It renders content from a DOM and it is expensive. Please replace it with once a second progress indication in a cheaper way, then OpenCode Desktop's CPU using should be fixed. At least this aspect of it.
Plugins
None
OpenCode version
v1.14.29
Steps to reproduce
- Run any conversation with a slow frontier model, which thinks a lot.
- Watch the process CPU loads while the conversation is getting processed.
- Observe the progress indication on screen.
- Log/measure the embedded browser update frequency and make your conclusion.
Screenshot and/or share link
Operating System
Linux Min 22.3 (Zara) (roughly Ubuntu 24.04)
Terminal
None, desktop app
Activity
[-]OpenCode Desktop is spending too much CPU power on animating a progress spinners[/-][+]OpenCode Desktop is spending too much CPU power on animating progress indicators[/+]github-actions commentedon Jun 26, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about the animation/rendering frequency (spinner and icon color transitions) rather than GPU acceleration, it may still be a distinct report worth keeping open. Please check the above and comment if your issue is different.
[-]OpenCode Desktop is spending too much CPU power on animating progress indicators[/-][+]OpenCode Desktop App is spending too much CPU power on animating progress indicators[/+]viktor-ferenczi commentedon Jun 26, 2026
I've got a stale OpenCode Desktop version 1.14.29, the upgrade failed every time.
Properly cleaned up the old version and upgraded to 1.17.11.
This kind of CPU usage problem is apparently gone on this version, so closing this issue.