Codex agents: Lock to one project folder
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
CLI
What feature would you like to see?
I love the addition of codex agents in 0.149.0 - that's a serious Claude leveller and increases my temptation to move away from Claude Code as a daily driver, great work.
I can see areas where codex's agents already beats claude's, but one significant area where it doesn't is allowing me to run codex agents in one project's folder only. An agent view that lists all my projects and all my sessions from all my projects gets too crowded to be usable very quickly. With claude agents I can pass in a --cwd and start one copy of agents per active project (i.e. per terminal tab). It'd be great to be able to do that in a codex agents view too.
Additional information
No response
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 at the CLI entry point for codex agents and inspect how it discovers and displays sessions across projects. Trace how command-line options are parsed, then determine how a project-folder scope could be passed to the agents view. Done means an invocation can restrict the view to one project folder while existing behavior remains available without that restriction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100