Codex CLI treating interal tool calls as MCP tool calls - requiring truncation and reading 200 lines maximum in local files

Resolved 💬 6 comments Opened Nov 16, 2025 by colsonj Closed Nov 16, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.57.0 & 0.58.0

What subscription do you have?

Pro

Which model were you using?

gpt-5-codex-high

What platform is your computer?

Windows 11 - running codex through WSLUbuntu-22.04

What issue are you seeing?

When writing a prompt to read a specified local file for context or otherwise, I will receive a message that the file is over 10kb and that it will need to truncate the message and that it will read only 200 lines.

What steps can reproduce the bug?

Produced bug: Read docs/foo.md so you understand the goal, scope, DoD, and contracts. Then do action... etc

Skips error but proceeds: Read section X in docs/foo.md and do action... etc

The second prompt will "work" because it will instead only read the first 200 lines after finding the title/section within the file. It still performs terribly as it doesn't read the full file for context.

What is the expected behavior?

As this is a local file and not asking codex to use an MCP tool call, it should read the whole file for context.

Additional information

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6544
  • #6426
  • #6415
  • #6259

Powered by Codex Action

cktang88 · 9 months ago
colsonj · 9 months ago
Is this the same issue referenced in https://x.com/badlogicgames/status/1989858718096228597?s=20 and acknowledged by https://x.com/thsottiaux/status/1989940347494084683?s=20?

Yep, that seems to be the same. Will close the issue

vzaliva · 7 months ago

I have this problem with Codex v0.79.0

vzaliva · 7 months ago

this issue must be re-opened

etraut-openai contributor · 7 months ago

@vzaliva, this bug report is quite stale at this point. If you think you're seeing something similar that you'd like to report, please fill out a new bug report and provide the requested information. Use the /feedback slash command to upload logs and session details.