codex - 💡(How to fix) Fix MCP running-tool label lowercases internal capitalization (`ListSomething` → `Listsomething`) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17766Fetched 2026-04-15 06:28:48
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3unlabeled ×1

Code Example

{
      "name": "mcp__serverName__ListSomething",
      "title": "ListSomething",
      "annotations": { "title": "ListSomething" },
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": { "type": "string" }
        },
        "required": ["query"]
      }
    }

---

mcp__serverName__ListSomething({ "query": "test" })
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

[email protected]

What subscription do you have?

Business

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

In Codex VS Code, the in-progress running-tool label for MCP tools lowercases internal casing.

Example:

  • Intended tool display: ListSomething
  • Running label shown: Listsomething

This is a UI-label issue; tool invocation itself succeeds/fails independently as normal.

What steps can reproduce the bug?

  1. Register an MCP tool with internal capitalization and explicit display metadata:
    {
      "name": "mcp__serverName__ListSomething",
      "title": "ListSomething",
      "annotations": { "title": "ListSomething" },
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": { "type": "string" }
        },
        "required": ["query"]
      }
    }
  2. In Codex VS Code, ask the agent to invoke the tool:
    mcp__serverName__ListSomething({ "query": "test" })
  3. While the call is running, observe the spinner/status label in the transcript. Observed label: Listsomething.

What is the expected behavior?

The running-tool label should preserve capitalization and show ListSomething, ideally using MCP display metadata (title or annotations.title) when present.

Additional information

Server-side MCP metadata for this tool is already emitted as:

  • name: mcp__serverName__ListSomething
  • title: ListSomething
  • annotations.title: ListSomething

Invocation identifier is exact-case and callable as mcp__serverName__ListSomething. This appears limited to MCP tool label rendering in Codex VS Code.

extent analysis

TL;DR

Update the Codex VS Code extension to properly handle MCP tool display metadata for running-tool labels, preserving internal capitalization.

Guidance

  • Verify that the title and annotations.title fields in the MCP tool's metadata are correctly set to ListSomething to ensure consistent display.
  • Check if the issue persists when using a different IDE or platform to isolate the problem to Codex VS Code on Windows.
  • Investigate the Codex VS Code extension's documentation for any configuration options or settings that may affect MCP tool label rendering.
  • Consider reporting the issue to the Codex VS Code extension developers, providing the reproduction steps and expected behavior.

Example

No code snippet is provided as the issue is related to the extension's behavior rather than a specific code implementation.

Notes

The issue appears to be specific to the Codex VS Code extension on Windows, and the root cause may be related to how the extension handles MCP tool metadata. Further investigation is needed to determine the exact cause and solution.

Recommendation

Apply workaround: Report the issue to the Codex VS Code extension developers and wait for a fix, as the problem seems to be related to the extension's behavior rather than a user-configurable setting.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING