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

> 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.

*Picture: Claude Code (saves the implementation handoff), Codex (checks it against the checkout) and Cursor (updates the review notes) connected to one 1folder holding Search handoff (a page saved by Codex, version 2) and Search review (a page saved by Cursor).* 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.

   *Picture: Adding 1folder to Claude Code by typing one line: claude mcp add --transport http 1folder https://1folderapp.com/mcp*
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.

   *Picture: 1folder’s Allow page: “Claude Code wants to use your 1folder”, with Only the folders I pick in Engineering and View and edit chosen, then 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.

   *Picture: Adding 1folder to Codex by typing one line: codex mcp add 1folder --url https://1folderapp.com/mcp*
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.

   *Picture: 1folder’s Allow page: “Codex wants to use your 1folder”, with Only the folders I pick in Engineering and View and edit chosen, then 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.

   *Picture: Adding 1folder to Cursor with this configuration: { "mcpServers": { "1folder": { "url": "https://1folderapp.com/mcp" } } }*
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.

   *Picture: 1folder’s Allow page: “Cursor wants to use your 1folder”, with Only the folders I pick in Engineering and View and edit chosen, then 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](https://1folderapp.com/integrations/claude-code-mcp.md) implementing one change, [Codex](https://1folderapp.com/integrations/codex-mcp.md) checking the result against acceptance criteria, and you deciding what to keep. A saved [handoff](https://1folderapp.com/how-to/claude-code-handoff.md) 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

| | Example | Why the next agent needs it |
|---|---|---|
| Goal | Keyboard-accessible file search | Defines the behaviour to verify |
| Code state | Branch search-focus at commit 8e1c2d4; two files not yet committed | Lets the next agent check that its checkout matches |
| Changed paths | Search input, results list, keyboard test | Points to the implementation without pasting all the code |
| Verification | Exact test command, result, and “phone check not run” | Separates observed results from unfinished work |
| Next action | Check focus after clearing a query with no results | Gives 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.

   *Picture: In Claude Code, you type: “Save Search handoff with the code revision and checks actually run.” Claude Code saves Search handoff (a page saved by Claude Code, version 1) to 1folder.*
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.

   *Picture: The versions of Search handoff: Checked keyboard focus (Codex, Just now); Saved the first handoff (Claude Code, 20 min ago).*

## 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](https://1folderapp.com/integrations/cursor-mcp.md) 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

- [Claude Code docs: MCP reference](https://code.claude.com/docs/en/mcp)
- [Claude Code docs: How Claude remembers your project](https://code.claude.com/docs/en/memory)
- [OpenAI documentation: Connect Codex to an MCP server](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
- [Cursor docs: Model Context Protocol](https://cursor.com/docs/mcp)

Checked on November 11, 2026.

## Read next

- [Claude Code vs Codex: compare the workflow, then try your task](https://1folderapp.com/compare/claude-code-vs-codex.md): Claude Code vs Codex from their own docs: where each runs, what the plans cost and how usage limits work. Plus how both share notes and handoffs in 1folder.
- [Claude Code MCP: add 1folder so your plans and handoffs are kept](https://1folderapp.com/integrations/claude-code-mcp.md): Add 1folder to Claude Code with one command. It saves plans, handoffs and reports you can open anywhere, and Codex, Cursor or ChatGPT can pick them up.
- [Codex MCP: add 1folder so Codex saves and reads your files](https://1folderapp.com/integrations/codex-mcp.md): Add 1folder to Codex with codex mcp add and sign in. Codex then saves handoffs and reports to your files, where Claude Code or ChatGPT can pick them up.
- [An AI agent workspace: shared files for every agent you use](https://1folderapp.com/use-cases/ai-agent-workspace.md): 1folder gives Claude Code, Codex, Cursor and your chat apps one shared workspace of files. Each agent gets its own access; every change is a version.

[Add 1folder to your AI app, free](https://1folderapp.com/signin) · [All resources](https://1folderapp.com/resources.md)

Website: https://1folderapp.com/ · Contact: hello@1folderapp.com