Yes. Claude Code and Codex can work on the same codebase. Give each a clear task, separate simultaneous file changes and use a written handoff when one continues the other’s work. Sharing a repository does not mean the tools automatically share their conversations, reasoning or current task state.
The simplest setup: implement, then review
Let one tool own a bounded change. When it finishes, save a Git checkpoint and give the second tool the task, changed files and verification results. Ask for a review before more editing starts.
For example, Claude Code could fix a Vue form while Codex reviews the resulting diff. You can reverse those roles. The useful distinction is ownership: the reviewer should know whether it is reporting findings or implementing a separate repair.
A handoff can be this short:
Goal: prevent the previous search response from replacing the latest results. Changed: the search controller and its tests. Verified: the repository tests passed. Still to check: keyboard interaction in the browser. Review the diff for incorrect state transitions and report evidence for each finding.
This is a fictional example. Replace it with the actual files and checks from your project.
For parallel work, use separate worktrees
A Git worktree provides another working directory and branch connected to the same repository. Git worktree documentation
After saving the intended starting state in a commit, run these commands from the repository root. Use unused branch and folder names:
git worktree add -b ai/form-fix ../site-form-fix HEAD
git worktree add -b ai/table-fix ../site-table-fix HEAD
Open one tool in each folder. Give one the form repair and the other the table repair. After reviewing both changes, integrate one at a time using your usual Git workflow, then run the combined checks.
Separate worktrees do not make overlapping designs compatible. If both tasks change the same shared component API, settle that contract first. Also check the development database, test accounts and ports: separate source directories can still point to the same external service.
Make sure both tools see the project rules
Codex loads AGENTS.md guidance. Codex project instructions
Claude Code v2.1.277+ can read AGENTS.md directly, subject to configuration and session availability. With default settings, a project CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md in the working directory or its ancestors prevents direct AGENTS.md loading. Alternatively, put @AGENTS.md in CLAUDE.md to import the shared file. Verify the loaded instructions. Claude Code memory
Keep shared build commands, architecture rules and acceptance criteria in one maintained place. Review existing instructions before adding wrappers or duplicating them.
What should you avoid?
Avoid two agents editing the same checkout at once without coordination. Avoid handing over only “continue”: include the current goal, completed work, test results and unresolved questions. Finally, treat a second AI opinion as another review input. Accept a finding when the code, reproduction or test supports it.
For a repeatable evaluation of each tool, see Claude Code vs Codex for frontend development.