In codex CLI, strange tool usage keeps repeating.
What version of Codex is running?
codex-cli 0.60.1
What subscription do you have?
Pro
Which model were you using?
gpt-5.1-codex-max
What platform is your computer?
Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64
What issue are you seeing?
• Ran git status -sb
• Ran echo "All set."
└ All set.
• Ran true
└ (no output)
• Ran echo 'Done again.'
└ Done again.
• Ran true
└ (no output)
• Ran echo 'Final done'
└ Final done
• Ran true
└ (no output)
---
in another session,
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && git status
│ --short
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
• Ran cd /home/ginis/wastelite-suite/wastelite_frontend && true
└ (no output)
What steps can reproduce the bug?
Uploaded thread: 019a9f7f-35ef-7293-80c6-21a61cd1bc33
What is the expected behavior?
There should be no strange tool executions.
Additional information
_No response_
7 Comments
Similar problem here. I have to currently monitor and stop it when I see it happen. Someone else told me it also ran git reset unnecessarily, destroying in progress work.
The fact that it always tries to
cdinto a directory it's already in before each command is also so incredibly frustrating. Been seeing this a lot as well lately. Telling it to stop doing it doesn't change a thing.I'm seeing this too, it also keep going for a very long time, doing tons of unnecessary tool calls. This is a snippet for when i asked it for a handoff prompt when i got tired of it not being able to solve the simplest of issues and forgetting AGENTS.md instructions.
GPT-5.1 does not do this (at least not from what i've seen thus far).
At which point i interrupted it as it looked like it was quickly spinning into mania.
Happens to me too with git status --short, every other turn it does it, even asked if it had any instruction for doing that, answered:
"No—there’s no rule requiring frequent git status. I’ll skip it unless it’s specifically useful (e.g., before a commit or when
you ask)."
model: gpt-5.1-codex-max xhigh
version: v0.60.1
thread ID 019a9f95-51c9-7132-b35c-6f0e791811f3
<img width="3456" height="2234" alt="Image" src="https://github.com/user-attachments/assets/e3195092-d166-4b07-9331-9f62ce6fe302" />
Stuck in a loop calling git status and diff commands.
Seeing this also - it starts getting "no output" and it becomes convinced that the commands it is running have no output and then it really gets confused and goes into wacky-land.
model: gpt-5.1-codex-max medium
version: v0.60.1
thread ID 019aa335-e2a4-7a50-8d18-d39fbddc5291
This appears to be a duplicate of #7010. Update to 0.61.0, and the problem should be gone.