[BUG] Claude Code Extension Spawning New `rust-analyzer` Processes For Every New Chat

Resolved 💬 3 comments Opened Feb 19, 2026 by AdamWhitehurst Closed Feb 22, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code Extension is spawning its own rust-analyzer process every time I start a new chat with /clear. This causes my machine to freeze by consuming all my memory (~6Gb per process but thats on rust-analyzer). Im using Cursor and only ever have one active chat.

What Should Happen?

Claude should use the existing rust-analyzer LSP server running in VSCode/Cursor or maybe a single rust-analyzer process for each active chat.

Error Messages/Logs

Steps to Reproduce

  1. Start Cursor
  2. Open claude code extension sidebar
  3. Type /clear a number of times

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.45

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Cursor

Additional Information

Btop after starting Cursor before opening claude extension:

<img width="2520" height="1516" alt="Image" src="https://github.com/user-attachments/assets/06c676d5-d883-437a-a0a0-0a4a06487f19" />

Btop after starting Claude Extension and /clearing twice:

<img width="2520" height="1516" alt="Image" src="https://github.com/user-attachments/assets/fe5e85dd-3007-4de2-9d5d-265391cdfd59" />

I've attached the output of ps aux | grep rust-analyzer | grep -v grep | awk '{print $2}' | xargs -I{} sh -c 'echo "=== PID {} ==="; cat /proc/{}/environ | tr "\0" "\n"' in a txt file.

ps aux grep rust-analyzer.txt

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗