Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Claude Desktop Linux - severe UI lag, Electron performance degradation on high-end hardware [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48299•Fetched 2026-04-16 07:03:42
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
ericvaelericvael
Participants
ericvaelericvaelgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Environment

  • Hardware: Intel i9 (20 cores), 64 GB RAM, RTX 4060, NVMe SSD (0% wear, SMART PASSED)
  • OS: Linux Mint / Ubuntu 24.04, kernel 6.8.0-110-generic
  • Claude Desktop: latest Linux version
  • Claude Code: 2.1.87
  • MCP plugins: ~14 plugin-dirs loaded simultaneously

Symptoms

  • Constant UI lag in Claude Desktop — typing, scrolling, and panel switching all stutter
  • Progressive degradation over the session: the longer the app runs, the worse it gets
  • Affects all interactions, not tied to a specific feature

Diagnostic performed

Full system diagnostic shows zero hardware bottleneck:

MetricValue
Load average1.5 / 2.1 / 2.0 on 20 cores (~10% utilization)
RAM11 GB used / 62 GB total, 51 GB available
Swap256 KB used / 2 GB
SSD I/O< 2% utilization, latency < 2ms
SSD health0% wear, 29°C
Claude Cache291 MB (clean)
Code Cache158 MB
vm_bundles37 MB
~/.claude.json22 KB

The Electron zygote process alone consumes 20% CPU and 600 MB RAM — disproportionate for a chat UI.

Key observation

Claude Code in terminal on the same machine is instantaneous. The problem is 100% in the Electron rendering layer, not the backend or the API.

Possible aggravating factor

14 MCP plugin directories are loaded per agent session. Each agent subprocess spawns with all --plugin-dir flags. This may contribute to memory pressure and IPC overhead within Electron.

Related issues

  • #26302
  • #31643
  • #42045
  • #4896

Request

  • A performance roadmap for the Electron app on Linux (renderer process optimization, IPC batching, lazy plugin loading)
  • Or consideration for a lighter-weight native Linux client

This is from a daily power user — the lag makes extended work sessions impractical.

extent analysis

TL;DR

Disabling or reducing the number of MCP plugins loaded simultaneously may alleviate the UI lag in Claude Desktop.

Guidance

  • Investigate the impact of the 14 MCP plugin directories on the Electron rendering layer, as they may be contributing to memory pressure and IPC overhead.
  • Try loading a minimal set of essential plugins to see if the performance improves.
  • Consider implementing lazy plugin loading to reduce the initial load on the Electron process.
  • Monitor the CPU and RAM usage of the Electron zygote process after making these changes to assess their effectiveness.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a configuration or optimization approach.

Notes

The issue seems to be specific to the Electron rendering layer, and the fact that the Claude Code in the terminal is instantaneous suggests that the backend and API are not the cause of the problem. The high CPU and RAM usage of the Electron zygote process, combined with the large number of MCP plugins loaded, points towards a performance optimization issue.

Recommendation

Apply workaround: reducing the number of MCP plugins or implementing lazy loading, as this approach addresses the likely cause of the performance issue without requiring significant changes to the underlying codebase.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING