400 400 Bad Request\n

[niksacdev]

Describe the bug

After working with copilot on a session for a while, the terminal seems to stop working and continuously throws a 404 Bad Request error.

I am using GH Copilot Enterprise, Model is Claude 4.5 and I am using Copilot CLI on macOS as well as linux (same issue on both environments).

Model call failed: {"message":"messages.208: `tool_use` ids were found without `tool_result` blocks immediately after: 
  toolu_vrtx_0141eaktmYg2JwxACYA4wnAg, toolu_vrtx_01BZq2c7FhvzSkje1zG5JSR8. Each `tool_use` block must have a corresponding 
  `tool_result` block in the next message.","code":"invalid_request_body"}

× Model call failed: "400 400 Bad Request\n"

× Model call failed: "400 400 Bad Request\n"

× Model call failed: {"message":"messages.208: `tool_use` ids were found without `tool_result` blocks immediately after: 
  toolu_vrtx_0141eaktmYg2JwxACYA4wnAg, toolu_vrtx_01BZq2c7FhvzSkje1zG5JSR8. Each `tool_use` block must have a corresponding 
  `tool_result` block in the next message.","code":"invalid_request_body"}

× Model call failed: {"message":"messages.208: `tool_use` ids were found without `tool_result` blocks immediately after: 
  toolu_vrtx_0141eaktmYg2JwxACYA4wnAg, toolu_vrtx_01BZq2c7FhvzSkje1zG5JSR8. Each `tool_use` block must have a corresponding 
  `tool_result` block in the next message.","code":"invalid_request_body"}

× Model call failed: "400 400 Bad Request\n"

Affected version

No response

Steps to reproduce the behavior

1. Continue working on a session, when the context gets long enough, the 404 errors start coming

Expected behavior

The session should just keep working without having a 404 errors
If the issue is context token length, then a /compact option should be available to keep the session alive

Additional context

No response

[williammartin]

What version are you on? We fixed something here yesterday.

[ws-work]

same, my copilot is @github/copilot@0.0.343

[niksacdev]

taken latest and will close for now, thank you!