Codex got very lost debugging a C crash that resulted from stubs that Codex had itself created

What version of Codex is running?

codex-cli 0.58.0

What subscription do you have?

Business

Which model were you using?

gpt-5.1-codex

What platform is your computer?

macOS

What issue are you seeing?

See uploaded logs and title of this issue. Codex burned many tokens trying to debug a memory-related crash in a C library (legacy dependency for the large C application refactor I'm working on). The cause turned out to be incomplete stubs that Codex had itself created. It took multiple sessions for it to finally find the root cause and is now making progress again, but it should have been "smart" enough to check this, or at least to document the stubs itself. I added guidance in AGENTS.md to avoid this situation in the future.

What steps can reproduce the bug?

Uploaded thread: 019a8e67-95d2-7c91-8f94-47341d795a21

What is the expected behavior?

_No response_

Additional information

_No response_