Troubleshooting changedtroubleshooting
Nearest release: v2.1.305, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 18:23 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+49added
Lines−39removed
From line
41
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits16to this page, all time
### Stray `>0q` at startup or `>4m` after exit
The whole hunk
from line 41, old and new numbered
/
from line 41
4141
4242If memory usage stays high after these steps, run `/heapdump` to write two files to `~/Desktop`: a JavaScript heap snapshot named `<session-id>.heapsnapshot` and a memory breakdown named `<session-id>-diagnostics.json`. Claude Code [hides the command from the command menu](/docs/en/commands#how-the-command-menu-matches-what-you-type); type it in full. On Linux without a Desktop folder, the files are written to your home directory.
4343
44<Warning>
45 The `.heapsnapshot` file contains every string in the process, including your full conversation and credentials. Don't attach it to a public issue or share it.
46</Warning>
44> [!WARNING]
45>
46> The `.heapsnapshot` file contains every string in the process, including your full conversation and credentials. Don't attach it to a public issue or share it.
4747
4848The command also prints a summary in the conversation, showing the process's total memory, how much of it is in the JS heap, and how much sits outside the heap. The summary also lists any leak indicators, such as a high memory growth rate or an unusually high number of open handles. The summary says whether most memory is in the JS heap, which the snapshot captures, or in native memory, which it doesn't.
4949
from line 87
8787
8888If characters render as boxes, smears, or the wrong glyphs when running Claude Code in the VS Code, Cursor, or Devin Desktop integrated terminal, the terminal's GPU renderer is likely the cause. Run `/terminal-setup` inside Claude Code to set `terminal.integrated.gpuAcceleration` to `"off"`, or set it manually in your editor settings and reload the window. See [Terminal configuration](/docs/en/terminal-config) for the other settings `/terminal-setup` writes.
8989
90### Stray `>0q` at startup or `>4m` after exit
91
92These characters, printed by terminals built on a VTE library older than 0.53, are the ends of two Claude Code control sequences. To stop the text, [update Claude Code](/docs/en/setup#update-claude-code) to v2.1.301 or later, which skips both sequences when it identifies such a terminal.
93
94If the text remains, print the VTE version from the terminal's shell:
95
96```bash theme={null}
97echo $VTE_VERSION
98```
99
100On a VTE-based terminal, a result below `5300` means a library older than 0.53: update or replace the terminal to get VTE 0.53 or later. Otherwise, see [Get more help](#get-more-help).
101
90102### Mouse wheel scrolls one line at a time in fullscreen rendering
91103
92104In [fullscreen rendering](/docs/en/fullscreen), Claude Code scrolls the conversation itself rather than leaving it to your terminal. If each wheel notch moves fewer lines than you want, run `/scroll-speed` to raise the number of lines per notch and save it, or set the `CLAUDE_CODE_SCROLL_SPEED` environment variable, except in the JetBrains IDE terminal, where Claude Code applies its own scroll handling and neither takes effect. See [Mouse wheel scrolling](/docs/en/fullscreen#mouse-wheel-scrolling) for the values each accepts.
from line 128
116128
117129If the Search tool, `@file` mentions, custom agents, or custom skills aren't finding files, the bundled `ripgrep` binary may not run on your system. Install your platform's `ripgrep` package and tell Claude Code to use it instead:
118130
119<Tabs>
120 <Tab title="macOS">
121 ```bash theme={null}
122 brew install ripgrep
123 ```
124 </Tab>
131**macOS**
125132
126 <Tab title="Ubuntu/Debian">
127 ```bash theme={null}
128 sudo apt install ripgrep
129 ```
130 </Tab>
133```bash theme={null}
134brew install ripgrep
135```
131136
132 <Tab title="Alpine">
133 ```bash theme={null}
134 apk add ripgrep
135 ```
137**Ubuntu/Debian**
136138
137 `ripgrep` is in Alpine's community repository. If `apk` reports that the package is missing, see [Alpine Linux setup](/docs/en/setup#alpine-linux-and-musl-based-distributions).
138 </Tab>
139```bash theme={null}
140sudo apt install ripgrep
141```
139142
140 <Tab title="Arch">
141 ```bash theme={null}
142 pacman -S ripgrep
143 ```
144 </Tab>
143**Alpine**
145144
146 <Tab title="Windows">
147 ```powershell theme={null}
148 winget install BurntSushi.ripgrep.MSVC
149 ```
150 </Tab>
151</Tabs>
145```bash theme={null}
146apk add ripgrep
147```
152148
149`ripgrep` is in Alpine's community repository. If `apk` reports that the package is missing, see [Alpine Linux setup](/docs/en/setup#alpine-linux-and-musl-based-distributions).
150
151**Arch**
152
153```bash theme={null}
154pacman -S ripgrep
155```
156
157**Windows**
158
159```powershell theme={null}
160winget install BurntSushi.ripgrep.MSVC
161```
162
153163Then set `USE_BUILTIN_RIPGREP` to `0`, either in your shell [environment](/docs/en/env-vars) or in the `env` block of your [`settings.json`](/docs/en/settings-reference#all-settings):
154164
155165```json theme={null}
from line 176
166176
167177Disk read performance penalties when [working across file systems on WSL](https://learn.microsoft.com/en-us/windows/wsl/filesystems) may result in fewer-than-expected matches when using Claude Code on WSL. Search still functions, but returns fewer results than on a native filesystem.
168178
169<Note>
170 `claude doctor` shows Search as OK in this case.
171</Note>
179> [!NOTE]
180>
181> `claude doctor` shows Search as OK in this case.
172182
173183**Solutions:**
174184
No line in this hunk matches that.