Tool call IDs from GLM-5/Kimi models exceed OpenAI's 64-character limit #8997
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
When using GLM-5 or Kimi models, tool call IDs are generated that exceed
OpenAI's Responses API 64-character limit, causing HTTP 400 errors:
OpenAI API error: POST "https://api.openai.com/v1/responses": 400 Bad Request {
"message": "Invalid 'input[24].call_id': string too long.
Expected a string with maximum length 64, but got a string with
length 210 instead.",
"type": "invalid_request_error",
"param": "input[24].call_id",
"code": "string_above_max_length"
}
Debug information
Conversation ID: 406ae4eb-feb5-4aa3-800d-dd0f59a552a0
Warp's backend needs to add ID sanitization:
// In the request handler before sending to OpenAI
const MAX_CALL_ID_LENGTH = 64;
function sanitizeCallId(id: string): string {
if (id.length <= MAX_CALL_ID_LENGTH) {
return id;
}
// Option 1: Truncate
return id.slice(0, MAX_CALL_ID_LENGTH);
// Option 2: Hash (prevents collisions)
// const hash = crypto.createHash('sha256').update(id).digest('hex');
// return call_${hash.slice(0, 12)}; // 17 chars total
}
Does Not Reproduce in
Opencode or Claude code
To reproduce
Reproduction
- Start a conversation with GLM-5 or Kimi model
- Make multiple tool calls (read files, run commands, etc.)
- Continue conversation for several turns
- Error appears and session becomes unrecoverable
Expected behavior
Expected behavior
Warp should sanitize/truncate tool call IDs to 64 characters before
sending to OpenAI's Responses API, similar to how OpenClaw fixed this
in openclaw/openclaw#31934
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
Kali Linux 2026.1, Windows 11 Pro, Windows Server 2022, Ubuntu 24.04 LTS, ,Ubuntu 22.04 LTS
Shell Version
No response
Current Warp version
v0.2026.03.25.08.24.stable_05
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
Noticed issue 2 weeks ago and has become more prevalent
Additional context
Our Linux Workstations of Ubuntu run GNOME
Company Kali Linux workstations run:
• Desktop Environment: XFCE 4.20 (xfce4-session 4.20.4)
• Display Server: X11
• Display Manager: LightDM (/usr/sbin/lightdm)
• Session: lightdm-xsession
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None