Alcoven

Can you share a ChatGPT project with Claude?

Blog · Published 30 September 2026 · Updated 11 November 2026

Not directly. ChatGPT and Claude each keep projects inside their own app, and neither offers a setting, connector or import that opens a project from the other. You can copy a project’s files and instructions across, export what you need, or keep the material in a doc both can read. If you want one project that both AIs keep reading and writing, it has to live outside both, and each AI opens it through MCP or, for coding agents, through git.

Say your strategist works in a ChatGPT project and your designer works in Claude. Here is what each route gives them, and what it costs.

Is there a ChatGPT connector for Claude?

No. A ChatGPT project keeps chats, files and instructions together, and in a shared project ChatGPT can draw on all of it, other members’ chats included. A Claude project has its own knowledge (the files you add) and its own instructions, and each person’s chats in it stay private unless they share one. Nothing in either app’s project settings points at the other, and neither company lists a connector that opens the other’s projects.

Both apps also remember. ChatGPT can reference other chats in the same project, and Claude gives each project its own memory. Each app’s memory stays inside that app, so neither reads what the other has learned.

Two official features come close, and both move a copy, once:

  • Claude’s memory import. In Claude, go to Settings > Memory and select “Start import”. Claude gives you a prompt to paste into ChatGPT; you paste ChatGPT’s answer back, and Claude stores it as memory entries. It is available on Free, Pro, Max, Team and Enterprise, and Anthropic calls it experimental. It carries what ChatGPT knows about you. The project’s files and chats stay where they are.
  • ChatGPT’s data export. Settings > Data controls > Export sends you a ZIP with your chat history and other account data. It can take up to seven days to arrive, the link expires 24 hours after it does, and it is not available in Business or Enterprise workspaces.

How do you use ChatGPT and Claude together on one project?

People do one of three things.

Copy the files and instructions across

This is the quickest route for one person:

  1. In ChatGPT, open the project’s sources list and download the files you need.
  2. Open the project’s menu (•••), select Project settings, and copy the instructions.
  3. In a project chat, ask ChatGPT to summarise the decisions and open questions so far, and copy the answer.
  4. In Claude, create a project, click “+” to add the files and the summary to its knowledge, and paste the instructions into “Set project instructions”.

From then on you have two copies. Every new file, changed instruction and fresh conclusion has to go into both, by someone who remembers to, and the chats stay in ChatGPT.

Export, then import

This suits one person moving from ChatGPT to Claude for good. For two people sharing a project, an export is a snapshot: it can take days to arrive, it belongs to the account that asked for it, and it goes out of date with the next chat.

Keep a doc both can read

Both apps read Google Drive. In ChatGPT you can paste a Drive file or folder link into a private project as a source. In Claude you can add a Google Doc to a private project’s knowledge, and Claude works from the latest version of it. Claude turns this off in shared projects, and OpenAI’s steps start from a private project, so in practice each person points their own project at the same doc.

The doc is only as current as the last person who edited it. The work still happens in each person’s chats, and what reaches the doc is whatever someone copies in, or asks their AI to write there.

What does each approach cost?

For one person moving across, copying or exporting is enough. For two people working on the same project week after week, all three leave someone keeping the copies in step.

Approach What reaches Claude What stays behind Who keeps it current
Copy files and instructions The files, the instructions, a summary The chats, and what ChatGPT remembers from them Whoever remembers to copy again
Export, then import The chats you pick from the download; your personal memory, through the import Everything added after the export Nobody: it is a snapshot
A doc both read What is written in the doc The chats on both sides Whoever edits the doc

Can ChatGPT and Claude open the same project?

Yes, when the project lives outside both of them, though on ChatGPT it depends on your plan. Two routes do this today.

Through MCP. The Model Context Protocol is an open standard that lets an AI app use tools and data held somewhere else. Claude adds an MCP server as a custom connector on every plan: Free allows one, and on Team and Enterprise an owner adds it for the organisation first. In ChatGPT the plan decides. OpenAI’s help centre, read on 22 October 2026, says a custom MCP server is added from Plugins in ChatGPT on the web, with no need to turn on developer mode first. Full support, read and write, is on Business, Enterprise and Edu. On Business only an admin or owner adds the server and publishes it for the workspace; on Enterprise and Edu an admin can also let chosen members add one. On Pro a custom MCP server can only read and fetch, and the page lists no way to add one on Free, Go or Plus. Check your plan’s page before you count on it.

Through git, for coding agents. If the project is a repository, both sides already read the same files. Codex reads a repository’s AGENTS.md before it starts work. Claude Code reads CLAUDE.md, and recent versions read AGENTS.md when there is no CLAUDE.md. One file in the repository can brief both tools.

Either way, each person opens the project from the AI they already use, where their plan allows it, and what one AI writes there, the other reads the next time it opens the project.

Can ChatGPT and Claude share memory?

No: as of 22 October 2026, neither app reads the other’s memory. ChatGPT’s memory draws on your own past chats and saved memories, and, depending on your plan and region, your Library files and connected apps. In a shared ChatGPT project, ChatGPT draws on every member’s chats and files there, and the project uses project-only memory, which keeps each member’s personal memory out. Claude builds memory from your chats and gives each project its own; on Team and Enterprise, where an owner allows memory, each member turns it on for themselves. Claude’s memory import, described above, copies what ChatGPT knows about you, once.

Notion now offers memory outside both apps. Its release notes of 19 October 2026 say Notion overhauled its MCP server so your agents “can use Notion as a shared brain”, to “find context, remember what matters, and make things you can share”, and that memory sync went live that day. Since Notion 3.8, released on 13 October 2026, an agent connected to Notion over MCP can read your workspace and update docs and task trackers, and Notion shows every change by every person and agent, with attribution. The release notes don’t say which Notion plans include memory sync, so check Notion’s plans before you count on it.

A project kept outside both apps, in a Notion workspace or a git repository, gives a team one record that the person on Claude and the person on ChatGPT both read and point to, and change where their plan allows it (see Through MCP above). Notion and git both show who made each change.

Where does Alcoven fit?

Alcoven keeps a project’s brief, documents and tasks, and every change to them, in one place, shared by the people and agents on it. The person on Claude adds Alcoven at https://app.alcoven.co/mcp. On ChatGPT Business, Enterprise or Edu, the same address goes in from Plugins; on Business, an admin or owner adds it for the company’s ChatGPT workspace. Each person signs in once and reaches every project they’re on. Whoever works in Claude Code or Codex clones the project with git and pushes. Each person’s own AI does the reading and writing (Alcoven runs no model for this), and whatever it changes comes back under that person’s name, for everyone on the project. Every document keeps every past version, and when you open one in the Alcoven app you see what others changed since you last read it, and who changed it. Each person’s sign-in reaches only their own projects, so other projects stay out. Free covers one project and up to five people writing to it, with no card. Start a project free

Sources

First checked on 30 September 2026; every source re-checked on 22 October 2026; Notion’s release notes read on 11 November 2026.