Getting error on gpt models

[iamasghar]

Summary

Error: 400 [OpenAI] Invalid 'input[10].name': string too long. Expected a string with maximum length 128, but got a string with length 134 instead.

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: e22dabbdaa260b594df3640bc7ec0040

Expected Behavior

Error: 400 [OpenAI] Invalid 'input[10].name': string too long. Expected a string with maximum length 128, but got a string with length 134 instead.

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: e22dabbdaa260b594df3640bc7ec0040

Actual Behavior

Error: 400 [OpenAI] Invalid 'input[10].name': string too long. Expected a string with maximum length 128, but got a string with length 134 instead.

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: e22dabbdaa260b594df3640bc7ec0040

Steps to reproduce the issue

Error: 400 [OpenAI] Invalid 'input[10].name': string too long. Expected a string with maximum length 128, but got a string with length 134 instead.

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: e22dabbdaa260b594df3640bc7ec0040

Command Code Version

Unknown

Operating System

Windows

Terminal/IDE

Unknown

Shell

cmd.exe

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

No response

[Coding-Dev-Tools]

The OpenAI rejection is a valid failure mode, but the current normal MCP registry path should prevent it. The issue is therefore most likely one of:

• a bypass path that sends mcpToolDefToSchema() output directly;
• provider-specific tools that do not pass through createMcpRegistry;
• gateway-side tool reconstruction;
• replayed or persisted tool schemas created before sanitization;
• another MCP integration path not covered by the registry.

The exact offending tool name is not included in the public issue, so the root cause cannot yet be confirmed.
Recommended priority: P2 investigation for now. Keep P1 if the trace proves this occurs through a supported, common MCP configuration.

Required fix:

The maintainers should add a final invariant immediately before every provider request: for every tools[*].name:

assert name.length <= providerLimit

That guard must cover all tool sources, not only MCP.

If an alias is required:

• generate it deterministically;
• guarantee collision resistance;
• retain a reverse map for tool execution;
• test the alias and original-name call path together.

If aliasing is unsafe, fail before the request with:

MCP tool '/' has a provider-invalid name of 134 characters.
Maximum supported length is 128.
Required tests:

• 127-character name;
• 128-character name;
• 129+ character name;
• two names that collide after truncation;
• tool invocation through the generated alias;
• provider/custom-agent tools that bypass the MCP registry;
• preflight rejection before network transmission.