Codex does not recognize "<repo>" string in prompt as meaning 'workdir'.

Resolved 💬 1 comment Opened Dec 17, 2025 by jmarkmorris Closed Dec 17, 2025

What version of Codex is running?

v0.73.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.1-codex-max high

What platform is your computer?

Darwin 24.6.0 x86_64 i386

What issue are you seeing?

Codex does not recognize "<repo>" string in prompt as meaning 'workdir'.

  1. start codex from your repo directory /Users/xxx/yyy/myrepo.
  2. prompt codex to create a file names '<repo>/file.md'
  3. codex can get confused and put your file in /Users/xxx/yyy/myrepo/myrepo/file.md

So it technically puts the file where you asked, but the user expected codex to understand that <repo> was intended to mean 'workdir'.

What steps can reproduce the bug?

Codex does not recognize "<repo>" string in prompt as meaning 'workdir'.

  1. start codex from your repo directory /Users/xxx/yyy/myrepo.
  2. prompt codex to create a file names '<repo>/file.md'
  3. codex can get confused and put your file in /Users/xxx/yyy/myrepo/myrepo/file.md

So it technically puts the file where you asked, but the user expected codex to understand that <repo> was intended to mean 'workdir'.

By the way, later in my session it recognized the confusion and asked if it could clean it up by moving the file to where I intended and deleting the redundant directory.

What is the expected behavior?

understand that <repo> (or equivalent) was intended to mean 'workdir'

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗