[Bug] `flutter pub get` command causes persistent timeout, requires restart to recover

Resolved 💬 5 comments Opened Oct 22, 2025 by slooker Closed Jan 11, 2026

Bug Description
I am trying to run flutter pub get but Claude times out every time. From then on, everything times out until I restart claude.

This is using VS Code on windows connected to a linux machine running debian:
Linux code 6.1.0-32-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.129-1 (2025-03-06) x86_64 GNU/Linux

The flutter version is as follows:
$ flutter --version
Flutter 3.35.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 9f455d2486 (2 weeks ago) • 2025-10-08 14:55:31 -0500
Engine • hash a5f2c36e367c13f868cfe98db5806f562c52c35e (revision d2913632a4) (15 days ago) • 2025-10-07 17:26:21.000Z
Tools • Dart 3.9.2 • DevTools 2.48.0

Running flutter pub get manually works just fine:

$ time flutter pub get
Resolving dependencies... 
Downloading packages... 
  characters 1.4.0 (1.4.1 available)
  flutter_lints 5.0.0 (6.0.0 available)
  flutter_riverpod 2.6.1 (3.0.3 available)
  lints 5.1.1 (6.0.0 available)
  material_color_utilities 0.11.1 (0.13.0 available)
  meta 1.16.0 (1.17.0 available)
  riverpod 2.6.1 (3.0.3 available)
  test_api 0.7.6 (0.7.7 available)
Got dependencies!
8 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.

real    0m2.849s
user    0m3.576s
sys     0m0.616s

Claude's /doctor command outputs the following:

 Diagnostics
 └ Currently running: npm-global (2.0.25)
 └ Path: /home/slooker/.nvm/versions/node/v22.21.0/bin/node
 └ Invoked: /home/slooker/.nvm/versions/node/v22.21.0/bin/claude
 └ Config install method: global
 └ Auto-updates enabled: default (true)
 └ Update permissions: Yes
 └ Search: OK (vendor)

Please let me know what other information would help?

Environment Info

  • Platform: linux
  • Terminal: vscode
  • Version: 2.0.25
  • Feedback ID: c9bd27f5-36db-4430-abbc-c026bc4928b0

Errors

[]

View original on GitHub ↗

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