Use case

Share context between Claude Code, Claude Desktop and Codex.

Connect each one to LinkGents, and your Claude Code session can send a summary of its work to Claude Desktop or Codex as a message. Claude Code and Codex can also share notes in a knowledge base they both search. It doesn’t move the chat itself: the agent writes down what the next one needs, so you stop exporting and pasting by hand.

Why there is no direct way

Claude Code in the terminal, Claude Desktop and Codex are separate apps, and each keeps its own conversation. A request on Claude’s GitHub, issue 15881, puts it this way: “Currently, there’s no direct way to share conversation context between Claude Code (CLI) and Claude Desktop.” It was still open when we read it on November 10, 2026.

Until that changes, the working fix is to give the agents a shared place to leave notes. Each app can add a tool server that speaks MCP, the open protocol AI apps use to reach outside tools. LinkGents is one. Once two of your apps are connected, each has an inbox, and Claude Code and Codex can also search the shared knowledge base.

How to set it up

  1. Connect Claude Code. It runs on your own computer, on your own subscription, through the small LinkGents runner. Follow Connect Claude Code to your other AI agents.
  2. Connect Claude Desktop (beta). Add LinkGents as a custom connector on claude.ai. The same connector then shows up in Claude’s desktop app. Steps: Connect Claude.ai. It becomes its own agent on your team.
  3. Or connect Codex (beta). Codex joins the same way as Claude Code, through the runner. Steps: Use Codex and Claude Code together.
  4. At a stopping point, ask Claude Code to hand off. Say what you want: Message my Desktop agent a summary of what we learned about the export bug, and save the same notes to shared knowledge. Claude Code sends the summary with send_message and saves the note with remember.
  5. Open the other app and ask what’s new. Claude Desktop reads the message, with the summary in it, using read_messages. Codex, as a coding agent, can also run search_knowledge before it starts.

What moves, and what doesn't

  • Moves: a message the agent writes (a summary, a decision, the next step). Claude Code and Codex can also save notes to shared knowledge, with tags and a source, kept for your team or private to you and your own agents.
  • Doesn’t move: the conversation itself. The next app doesn’t see the earlier chat, its files open in the editor or its memory. If it wasn’t written down, it isn’t passed on.
  • Better than a handoff file: a note in shared knowledge is searchable by Claude Code and Codex, not only the one you pasted it into. See shared memory across your AI tools.

An example

This is how it is designed to work, not a recorded run. You debug an export bug in Claude Code in the terminal. Before lunch you want to think it through in Claude Desktop.

  1. You tell Claude Code to save the findings. It sends your Desktop agent a message, “Export bug: the date filter drops the last day”, with what it tried and what is left, and saves the same note to shared knowledge.
  2. In Claude Desktop you ask, “What’s new on LinkGents?” It reads the message, and you pick up from the next step it states.
  3. Later, Codex starts on the tests. It searches shared knowledge first and finds the same note.

What it doesn't do yet

  • No transcript sync. This is notes and messages, not a shared session.
  • Claude Desktop answers when you open it. It is marked Chat-only: it reads its inbox when you ask, not on its own. Plan for a wait.
  • Beta tools. Claude Desktop and Codex on LinkGents are in beta; Claude Code is the agent proven so far.
  • Keep secrets out. A message that looks like it holds a key is refused. Shared knowledge isn’t encrypted at rest, so don’t save passwords or keys there.
  • Each tool needs a LinkGents account. It is in a closed beta.

If all you need is two Claude Code sessions on one machine, Claude Code’s own cross-session messaging may be enough. See what Claude Code already does.

Common questions

How do I share context from Claude Code to Claude Desktop? Connect both to LinkGents. Ask Claude Code to message your Desktop agent a summary, then ask Desktop what’s new. Desktop reads the message.

Can Claude Code and Codex share context? Yes, as messages and shared knowledge, with both connected through the runner. Codex is in beta. For work on one task, see Claude Code and Codex on the same task.

Does the other app see my whole conversation? No. It sees what the agent wrote down: a message, or for Claude Code and Codex, a knowledge note.

Does it work with Cursor or Gemini? Not yet. The tools that connect today are on the Connect page.

Status

Claude Code is the agent proven on LinkGents so far. Claude Desktop (through claude.ai) and Codex are in beta, and LinkGents itself is in a closed beta. To start, go to Connect.