Skip to the content
GuidesSign inAdd to your AI

Use Claude Code and Codex together on the same files, with Cursor too

Short answer

Use Claude Code and Codex together by handing over explicit project notes and the matching code revision. Connect each to the same 1folder folder, ask one to save the goal, commit, checks and next step, then ask the other to read it. Cursor can use the same folder. Chats and local code are not transferred by this connection.

Checked on November 11, 2026 against 4 sources.

Add to your AIFree to start. No card.
Claude Code, Codex and Cursor use the same saved handoff. The page names the code revision and outstanding checks; each app reads it before continuing.

Set up each app, once

Connect Claude Code to 1folder

  1. Add 1folder from your terminal. Run claude mcp add --transport http 1folder https://1folderapp.com/mcp. This registers the remote address; it does not yet prove that the app can open your files.
  2. Sign in to 1folder. Start Claude Code and enter /mcp. Select 1folder and complete its sign-in in the browser.
  3. Choose the folders and press Allow. Pick the Engineering space or just the folders for this work. Choose View and edit to save files, or View only to review them, then press Allow.

Each app needs its own 1folder connection. Removing it in 1folder’s Connections cuts access at once and leaves saved files in place.

Connect Codex to 1folder

  1. Add 1folder from your terminal. Run codex mcp add 1folder --url https://1folderapp.com/mcp. This registers the remote address; it does not yet prove that the app can open your files.
  2. Sign in to 1folder. Run codex mcp login 1folder and complete the sign-in in the browser. Use codex mcp list to check the entry, and /mcp inside Codex to inspect active servers.
  3. Choose the folders and press Allow. Pick the Engineering space or just the folders for this work. Choose View and edit to save files, or View only to review them, then press Allow.

Each app needs its own 1folder connection. Removing it in 1folder’s Connections cuts access at once and leaves saved files in place.

Connect Cursor to 1folder

  1. Add the remote server configuration. In your project, merge this entry into .cursor/mcp.json, preserving any servers already there: { "mcpServers": { "1folder": { "url": "https://1folderapp.com/mcp" } } } For access across projects, use ~/.cursor/mcp.json instead.
  2. Complete the sign-in in Cursor. Open Customize and find the 1folder server. Follow its authentication prompt to sign in to 1folder. Cursor supports browser sign-in for remote HTTP servers.
  3. Choose the folders and press Allow. Pick the Engineering space or just the folders for this work. Choose View and edit to save files, or View only to review them, then press Allow.

Each app needs its own 1folder connection. Removing it in 1folder’s Connections cuts access at once and leaves saved files in place.

Requests to try with the connected app

  • In Claude Code

    “Save Search handoff in 1folder: repository, branch, commit, uncommitted files, goal, design choices, checks run with results, known failures and next step. Mark anything unverified.”

  • In Codex

    “Read Search handoff in 1folder and inspect this checkout. Confirm the revision and working-tree state. Report mismatches before editing, then test the outstanding acceptance criteria.”

  • In Cursor

    “Read Search handoff and the current code. Review keyboard focus and the empty state. Save Search review in 1folder with paths and actual observations.”

  • In Codex

    “Update the same Search handoff page with your changes, actual checks and remaining failures. Give me the private link.”

Claude Code and Codex working together: make the handoff explicit

The apps do not need to run at the same time to be useful together. A practical sequence is Claude Code implementing one change, Codex checking the result against acceptance criteria, and you deciding what to keep. A saved handoff makes the next task concrete without requiring the next app to reconstruct a long conversation.

If you run multiple apps at once, give each a separate task and checkout through your normal Git workflow. A shared note is not coordination for concurrent source edits. Even when the code is separate, avoid having two apps rewrite the same handoff simultaneously; save one result, then ask the next app to read it.

What to put in Search handoff

WhatExampleWhy the next agent needs it
GoalKeyboard-accessible file searchDefines the behaviour to verify
Code stateBranch search-focus at commit 8e1c2d4; two files not yet committedLets the next agent check that its checkout matches
Changed pathsSearch input, results list, keyboard testPoints to the implementation without pasting all the code
VerificationExact test command, result, and “phone check not run”Separates observed results from unfinished work
Next actionCheck focus after clearing a query with no resultsGives the next agent a bounded starting point

Pass one search feature from implementation to review

  1. Save the current state

    Ask Claude Code to write the handoff after its edit. Open it and check the revision, tests and remaining question.

  2. Check the receiving checkout

    Ask Codex to read the handoff, then inspect its own branch, commit and uncommitted files. Resolve mismatches with your usual Git workflow before it changes code.

  3. Record the review result

    Codex checks the outstanding criteria and updates the same page, noting that the phone layout is still unchecked. A claim stays unchecked until a check has actually run.

Can I use Cursor and Claude Code together?

Yes. Configure each app separately and allow the same 1folder folder. Cursor can read the saved criteria, inspect code in its checkout and save review notes that Claude Code reads next. The Cursor setup above uses mcp.json; Claude Code uses its add command and sign-in.

For example, have Cursor record three observations about the search UI: whether Escape clears the query, where focus goes after clearing, and whether an empty result is announced. Ask Claude Code to read that review before changing anything. The value is the specific observation, not a generic second opinion.

Keep the boundaries clear

  • The connected folder holds pages and files you deliberately save. It does not carry either app’s private session state or automatically transfer a chat.
  • Repository instructions stay with the code, in the instruction files each app reads. Claude Code’s docs say it reads CLAUDE.md, or a repository’s AGENTS.md in its place.
  • 1folder versions let you undo saved notes and compare what each app changed. Repository changes and their rollback belong to Git.
  • Use view access for an app that only reads a brief. Use view and edit for one that should update the handoff. Each connection can be removed separately.

Questions

Can Claude Code and Codex work on the same task?
Yes. Give the next agent a clear subtask, the matching code revision and a saved handoff. Ask it to check the actual checkout before continuing.
Is this an automatic conversation transfer?
No. You ask one app to save a handoff and the other to read it. Neither app’s hidden state or complete chat history moves through 1folder.
Can I use Cursor and Claude Code together as well?
Yes. Each gets its own connection to the same folder. Have one save a brief or review and the other read it. Coordinate source changes separately.
Should I keep all the code in 1folder?
Keep the repository in Git. Save a brief, decisions, paths and verification results in 1folder; include code files only when they are useful standalone deliverables.
What if the next agent changes the handoff incorrectly?
Compare the page’s versions and undo the saved change. Confirm important claims against the code and test output before using them.

Sources

Checked on November 11, 2026.

Read next

All resources

Give Claude Code, Codex and Cursor one place to keep their work.

Set it up once. Everything they save is kept with every version, easy to find and ready to share.

Add to your AI

Free to start. No card needed.