It looks like there's an issue with the Codex adaptation.

[clliangchen]

I am attempting to initialize Codex according to the instructions in the Markdown documentation, but I am unable to use it.
Could you please take a look to see if there are any underlying issues?
I managed to resolve the problems myself using Codex, and there were two main issues:

1. I was unable to reference rtk within .codex/AGENTS.md using the @RTK.md syntax. My workaround was to copy the commands from RTK.md directly into agents.md; however, this is not a permanent solution, as any future updates to RTK.md would require me to manually update agents.md as well.
2. After making those modifications, rtk still encountered some permission issues; specifically, the default database path for rtk is located in a restricted directory, preventing the sandbox environment from creating or opening the file. My temporary fix was to edit rtk/config.toml and change the database_path to a writable location: .codex/memories/rtk/history.db. Again, this is merely a temporary workaround; could you please check if there is a more robust or permanent solution available?

[pszymkowiak]

[w] wshm · Automated triage by AI

🔍 Automated Triage

🐛 Category	bug
🟡 Priority	medium
🎯 Confidence	72%

Summary

Codex integration has two issues: @RTK.md reference syntax not working in .codex/AGENTS.md, and default database path falls in a restricted directory inaccessible from the Codex sandbox. Needs investigation of agent file inclusion and sandbox-aware default paths.

📁 Relevant files

• rtk/config.toml

---

Triaged automatically by wshm · This is an automated analysis, not a human review.

[Jeoffreybauvin]

Same issue here, Codex v0.116.0 installed with npm on Ubuntu 24.04. My coworker with Mac and codex installed with brew has no issue.