FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

CAIP 400: input item ID does not belong to this connection · Issue #2147 · github/copilot-cli · GitHub

Repository navigation

CAIP 400: input item ID does not belong to this connection #2147

Description

Describe the bug

✗ Execution failed: CAPIError: 400 
  {"error":{"code":"bad_request","type":"websocket_error","message":"input item ID does not belong to this connection"}} (Request ID:  00000-00a42e7c-787d-4a9b-bd97-ac57290bda5d) 

Model: gpt-5.4 (xhigh)

Affected version

GitHub Copilot CLI 1.0.8.

Steps to reproduce the behavior

  1. Write any prompt. After close and reopen the powershell terminal, I get the same thing.

Expected behavior

No response

Additional context

No response

Activity

added theissue type on Mar 18, 2026

cazlouk-partners commented on Apr 3, 2026

Hello, Any news about this bug ?

examon commented on Apr 7, 2026

This has been fixed as of v1.0.10. The root cause was stale WebSocket state being reused after a reconnection, which triggered the "input item ID does not belong to this connection" error. Updating to the latest version should resolve this. If you're still seeing this on a current version, please feel free to reopen.

jcousineaugd commented on May 27, 2026

This has been fixed as of v1.0.10. The root cause was stale WebSocket state being reused after a reconnection, which triggered the "input item ID does not belong to this connection" error. Updating to the latest version should resolve this. If you're still seeing this on a current version, please feel free to reopen.

This has NOT been fixed within VS Code. IDK about GH CLI, but this issue is still occurring within the chat interface of VS Code.
See microsoft/vscode#318482

DrEsteban commented on Aug 5, 2026

Still seeing this on Copilot CLI v1.0.79-4

lifengl commented on Aug 27, 2026

I ran into this on 1.0.81-12. It happened after I exited, restarted and resumed the session. It only recovered after switching between models.

logar16 commented on Sep 9, 2026

It happens to me if a session launches with a different user than I want (e.g. personal vs work) and does a message and then I switch user. It's like it's trying to access data that is keyed under the previous user or something and it just fails. I have to rewind conversation enough that it goes away seems like. Just restarting doesn't fix it.

felipepessoto commented on Sep 12, 2026

I was able to workaround the issue without losing the existing session by creating a /fork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL