github copilot problem #640
Replies: 4 comments 1 reply
|
=== REQUEST INFO === === HEADERS === === REQUEST BODY === === API REQUEST 1 === Headers: Body: === API RESPONSE === === RESPONSE === { |
|
Which client do you use? |
|
"User-Agent: oai-compatible-copilot/0.1" It's the GitHub Copilot client. |
|
I dug into the source to see if this is a known gap. Short version: it looks like it is. The error ( CLIProxyAPI does have an ID sanitizer for exactly this pattern — The request path that forwards history straight to a Claude upstream ( So: if a @ahmedrageh — could you paste one of the offending |
|
Thanks for the full dump — that pins it down. Look at the four The Given your model tag ( Hope the duplicated-blob observation saves someone the time of finding it independently — that pattern (identical suffix, different real ids) is the kind of thing that's easy to miss by inspection but jumps out once you diff a few IDs from the same request, like above. |
Uh oh!
There was an error while loading. Please reload this page.
=== REQUEST INFO ===
Version: 6.6.22
URL: /v1/chat/completions
Method: POST
Timestamp: 2025-12-17T13:18:32.8195707+03:00
=== HEADERS ===
User-Agent: oai-compatible-copilot/0.1.8 VSCode/1.107.0
Authorization: Bearer 12...56
Accept-Language: *
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Type: application/json
Sec-Fetch-Mode: cors
Accept: /
Content-Length: 111817
=== API RESPONSE ===
{
"error": {
"code": 400,
"message": "{"type":"error","error":{"type":"invalid_request_error","message":"messages.3.content.0.tool_use.id: String should match pattern '^[a-zA-Z0-9_-]+$'"},"request_id":"req_vrtx_011CWC66JdZ4zEgoGsShm311"}",
"status": "INVALID_ARGUMENT"
}
}
=== RESPONSE ===
Status: 400
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS
Access-Control-Allow-Headers: *
Content-Type: application/json
Cache-Control: no-cache
Connection: keep-alive
{
"error": {
"code": 400,
"message": "{"type":"error","error":{"type":"invalid_request_error","message":"messages.3.content.0.tool_use.id: String should match pattern '^[a-zA-Z0-9_-]+$'"},"request_id":"req_vrtx_011CWC66JdZ4zEgoGsShm311"}",
"status": "INVALID_ARGUMENT"
}
}
All reactions