Support for Codex seems broken
Open
Nobody has claimed this yet.
area:cli
bug
filter-quality
needs-reproduction
P1-critical
priority:high
- Dominant language
- Rust
- Stars
- 81k
- Forks
- 5.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 35
Description
I initialized rtk in the working folder with rtk init -g --codex, and it shows this:
RTK configured for Codex CLI.
RTK.md: ~/.codex/RTK.md
AGENTS.md: @~/.codex/RTK.md reference already present
Codex global instructions path: ~/.codex/AGENTS.md
Then I called codex and started working, until this happened consistently:
$ rtk grep -RIn "grep -oPm 20 '\(\?<= <title>\)\[\^<\]\+'\|sort -Vr \| head
│ -1\|sort -Vr \| \{\|eval \"\$\{TESTRELEASES" . --include='*.sh'
/usr/bin/grep: Unmatched \{
Same rtk version/installation works just fine in Claude Code (initializing with just rtk init -g of course).
Using rtk 0.35.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported setup with rtk init -g --codex and the shown rtk grep command under Codex CLI. Compare its behavior with the same RTK installation initialized for Claude Code, then trace the Codex integration path. Done means the command no longer produces /usr/bin/grep: Unmatched { in Codex while existing Claude Code behavior remains working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100