You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG - Desktop] High iGPU load 50% or more during task execution. #31664
The problem stems from two inefficient UI animations triggered during task execution ("working" status):
Progress Bar (session-progress-bar): The clip-path animation with rounding ( round 999px) requires Chromium to recalculate mask geometry and repaint layers every frame, leading to high GPU overhead.
Project Avatar Loader (project-avatar-v2-loader): The use of mix-blend-mode: soft-light for the spinning indicator prevents Chromium from using simple optimizations. It forces complex shader calculations for each frame across the entire tab panel and window title area.
Minimizing the window stops these processes (suspending requestAnimationFrame and CSS repainting), reducing load to 0%. When the window is active, both animations drive high GPU usage.
Plugins
I don't have any plugins.
OpenCode version
1.16.2 Desktop version
Steps to reproduce
Open the application and set the task to execute. Click the execute task button.
Thank you for updating the issue! It now meets our contributing guidelines. We appreciate the detailed description, steps to reproduce, and the hardware/system information. We'll look into the high iGPU load caused by the UI animations.
Confirmed on macOS (M1 Pro, 16GB): forcing prefers-reduced-motion: reduce drops GPU usage to near-zero immediately.
Repro: OpenCode Desktop with active sessions → DevTools → Rendering tab → "Emulate CSS media feature prefers-reduced-motion: reduce".
Before/after (btop + Activity Monitor, same sessions running):
GPU total: 61% → 5%, instantly after toggling
OpenCode Helper CPU: 36.7% → 9.9%
OpenCode Helper GPU (Activity Monitor): ~13% while working
This confirms the animations described in this issue account for essentially the entire GPU cost, and that the mitigation already works behind the prefers-reduced-motion media query — it just needs a persistent setting (or honoring the OS-level Reduce Motion, which the DevTools emulation proves works).
Baseline (Activity Monitor, OpenCode Helper at 13.3% GPU):
Before (btop, GPU 61%, OpenCode Helper 36.7% CPU):
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
github-actions commentedon Jun 10, 2026
Thank you for updating the issue! It now meets our contributing guidelines. We appreciate the detailed description, steps to reproduce, and the hardware/system information. We'll look into the high iGPU load caused by the UI animations.
brandon-julio-t commentedon Aug 6, 2026
Confirmed on macOS (M1 Pro, 16GB): forcing
prefers-reduced-motion: reducedrops GPU usage to near-zero immediately.Repro: OpenCode Desktop with active sessions → DevTools → Rendering tab → "Emulate CSS media feature prefers-reduced-motion: reduce".
Before/after (btop + Activity Monitor, same sessions running):
This confirms the animations described in this issue account for essentially the entire GPU cost, and that the mitigation already works behind the
prefers-reduced-motionmedia query — it just needs a persistent setting (or honoring the OS-level Reduce Motion, which the DevTools emulation proves works).Baseline (Activity Monitor, OpenCode Helper at 13.3% GPU):
Before (btop, GPU 61%, OpenCode Helper 36.7% CPU):
DevTools setting applied:
After (btop, GPU 5%, OpenCode Helper ~10% CPU):
opp4s commentedon Sep 4, 2026
Reproduced on macOS — v1.18.28
Same issue confirmed on macOS (Apple Silicon, 8GB RAM).
Process breakdown (idle state, no tasks running):
Key observations:
--disable-gpu,--disable-gpu-compositing,--use-gl=swiftshader, env vars) — none are respected by the appelectron-flags.conffile in the app support directory is ignoredImpact:
Environment:
This issue persists across restarts and version updates. The GPU process appears to be in a continuous rendering loop even when the UI is idle.
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊