The session has been destroyed

Summary

✖ CRITICAL: Uncaught Exception!
This is an unexpected error. Please file a bug report at https://github.com/CommandCodeAI/command-code/issues/new
✖ ERROR → Error
ℹ REASON → The session has been destroyed
ℹ ERROR STACK ↓
Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
at ClientHttp2Session.request (node:internal/http2/core:1813:13)
at requestStream (node:internal/deps/undici/undici:8763:26)
at writeH2 (node:internal/deps/undici/undici:8883:16)
at Object.write (node:internal/deps/undici/undici:8355:18)
at _resume (node:internal/deps/undici/undici:9749:54)
at resume (node:internal/deps/undici/undici:9682:7)
at node:internal/deps/undici/undici:9503:32

Trace ID: 25be7b1ac5c17e2a496f3eb5ac1c61d1

Expected Behavior

Command Code coding.

Actual Behavior

Command Code crashing.

Steps to reproduce the issue

nil. Happens randomly

Command Code Version

1.50.0

Operating System

macOS

Terminal/IDE

vscode

Shell

powershell

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

No response

Start by tracing the request path around ClientHttp2Session.request, requestStream, and writeH2 in the Node.js/undici stack, then inspect how Command Code manages HTTP/2 sessions. Try to capture the random failure on macOS with version 1.50.0; done means requests no longer crash when a session has been destroyed.