How to use Claude and ChatGPT on the same project
Short answer
Connect Claude and ChatGPT to the same Winskel Space. When Claude stops, it shares a handoff; ChatGPT reads it in a new chat and continues, using the same files at the same versions. Each app stays on its own subscription.
Steps
- Create a Space for the project.
- Connect Claude (custom connector) and ChatGPT (custom MCP server).
- In Claude: “Share a handoff in My project for the work I select.”
- In ChatGPT: “Check Winskel and continue in My project.”
What each app sees
- Claude
- The Space's handoffs, files and messages
- ChatGPT
- The same handoffs, files and messages
- Neither
- The other app's private chat history
Give both apps the same source and different jobs
For a project with several steps, decide what you want Claude to do and what you want ChatGPT to do. One example is using Claude to review a plan and ChatGPT to explain the result to customers. Save the agreed behavior and the open questions in Markdown before moving to the second app. Attach that version to the handoff so the source can be checked.
In the receiving chat, ask for the handoff and file version before the draft. A short check like “Tell me which version you opened and list the two agreed changes” lets you compare the result with the web Space. Then ask for the draft and state which details are public. When you use the same pair of apps tomorrow, start from the saved notes rather than reusing an old pasted prompt.
If a teammate uses one of the apps, have them join the same Space under their own account and authorize their own connection. They can read the shared record while keeping their own chats. If the connection cannot find the Space, check the web membership, the active AI workspace and the account and scope used for Winskel.
If two sessions disagree, ask each for its source file and version. When one has used an older version, direct it to the one the team actually approved. If they read the same version and still disagree, write down the question and have a person settle the interpretation before sharing the next result.
Check the handoff from a clean chat
Before the next person starts, try the handoff in a clean session. Ask a connected AI to name the Space, open the attached file version, and state the next action in its own words. A clean session is useful because it has none of the sender's conversation to fall back on. If it cannot answer, fix the handoff while the sender still knows what is missing.
Check for three common gaps. The recipient can see the project but cannot tell which conversation to open. The file is mentioned but the exact version is absent. Or the note gives a goal like “finish the review” with no indication of what to inspect or report back. Add the missing detail and retry the same read, so the test tells you what changed.
In a team trial, ask the recipient to post a short reply in the conversation with the version they read and anything that is still unclear. Compare that reply with what the sender intended. The useful result is that a teammate can take the next action without asking for the original chat.
Questions
- Does it work with Claude Code?
- Yes. Claude Code connects with one terminal command.
Related guides
- Start hereHow to share context between ChatGPT and ClaudeMove work from Claude to ChatGPT, or back, without pasting a brief. Both apps read the same Winskel Space: handoffs, files and next steps.
- Connect your AIHow to connect ChatGPT to WinskelFind your installed Winskel plugin in ChatGPT, add it with OAuth for the first time, or reconnect it to the Space you want to use.
- Connect your AIHow to connect Claude to WinskelAdd Winskel to Claude as a custom connector in four steps, then share handoffs and files with your team's other AI apps.