Tool calls issues on VS Code

Issues the maintainers labelled both platform:vscode and area:tools.

100 issues · 22 open · 78 resolved (78%) · first seen Feb 26, 2026

Is this getting better or worse?

This class of problem is converging. 36 new reports in the last 90 days vs 56 in the 90 before — -36%. The open backlog peaked at 23 in 2026-04 and sits at 22 today.

0 6 12 17 23 2026-022026-042026-062026-08
2026-02 — First reports2026-03 — Most new reports (22)2026-04 — Peak backlog (23 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

64 of these reports name the Claude Code build they were running, spanning 43 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 34 days across 78 closures. Of the 78 closures with a recorded reason, 15% were closed as completed and 66 as not-planned or duplicate. The most recent completed fix landed in 2026-07.

Workarounds reported by the community

33 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] AskUserQuestion: "No response after 60s — continued without an answer"
Another workaround is to temporarily add the tool to the . list in your . Any Tool added to that list is entirely hidden from the model, so it will simply ask questions in prose in the chat window.
Found in the thread of #73125 · resolved
[BUG] Claude abuses bash tools for reads, writes, and edits when running in Auto Mode
…managed settings and roll it out to all the engineers as a work around until this is fixed: You may get an instruction from the harness when running in Auto Mode to favor bash commands over native tools like Read, Edit.…
Found in the thread of #87971 · still open
[Bug] Parallel tool calls hang on Bash execution errors
…ocks → 400 wedges session), 63364 (full softbrick example). Workaround that holds: stay on 4.7, or set on 4.8 to remove parallel batches entirely (sequential, slower, but no cascade possible).
Found in the thread of #63881 · resolved
[BUG] CLAUDE_CODE_EXTRA_BODY thinking config breaks WebSearch and WebFetch on Opus 4.7 [1m]
…de Code (2.1.131) What's Wrong? I run with the following in as a workaround for 49322 (thinking summaries not rendering in VS Code extension on Opus 4.7): This restores thinking summaries in the VSCode extension. But it…
Found in the description of #56984 · still open
[BUG] bug in Claude Code's PDF parser
The "workarounds" don't work either -- the file has a lot of equations, figures and tables so converting to text doesn't help.
Found in the thread of #30819 · resolved

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–100

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. Tool calls issues on macOS

    1,676 issues
  2. Tool calls issues on Windows

    891 issues
  3. Tool calls issues on Linux

    676 issues
  4. IDE integration issues on VS Code

    1,307 issues
  5. Model behaviour issues on VS Code

    463 issues
  6. Terminal UI issues on VS Code

    230 issues
  7. Cost and usage issues on VS Code

    203 issues
  8. Permissions issues on VS Code

    176 issues