[Bug] Usage data loading hangs indefinitely in CLI
Resolved 💬 3 comments Opened Apr 18, 2026 by dandaka Closed Apr 22, 2026
Bug Description
Loading usage data…
and it never loads
While it always loads in the desktop client
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.1.112
- Feedback ID: 1e0ff428-8524-4b51-ae6e-171c08aa6c4d
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/dandaka/.local/share/claude/versions/2.1.112 (expected in multi-process scenarios)\n at Od_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n at Ke6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T15:30:32.469Z"},{"error":"Error: Failed to download binary from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.114/darwin-arm64/claude: The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch()\n at Up1 (/$bunfs/root/src/entrypoints/cli.js:2746:7713)\n at async zl9 (unknown)\n at async Dl9 (unknown)\n at async ap1 (unknown)\n at async Ml9 (unknown)\n at unknown\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-18T02:16:18.851Z"},{"error":"Error: The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch()\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12513)\n at emitError (node:events:43:23)\n at emitErrorNT (internal:streams/destroy:88:12)\n at emitErrorCloseNT (internal:streams/destroy:69:14)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async Fp1 (unknown)\n at async Up1 (unknown)\n at async zl9 (unknown)\n at async Dl9 (unknown)\n at async ap1 (unknown)\n at async Ml9 (unknown)\n at unknown\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-18T02:16:18.851Z"}]This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗