Codex refers to state of git (ie git status) as the worktree, in an environment where we are sensitive to whether worktrees are being used.

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.5 high

What platform is your computer?

Darwin 25.4.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

cmux 0.64.3

What issue are you seeing?

When referring to the state of the git repo (the main folder) using git status (ie not a worktree), it referred to the worktree as clean. However we were running a worktree somewhere else on this repo, so using worktree as a generic term for the git status is something that should be discouraged in future models. It's false precision, it doesn't actually mean a worktree, and all it does is cloud what the current state is.

After examination, the model was NOT running on a worktree at all.

What steps can reproduce the bug?

Uploaded thread: 019e1596-7b38-74d3-a874-a6eb0ef64835

What is the expected behavior?

It should refer to it perhaps as the git status, the work directory status, or almost anything but a worktree (which is a specific thing, that this is in fact not).

Additional information

_No response_