Claude Code Can Now Message Other Sessions: What Changes for Parallel Work?

August 8, 2026Updated: August 8, 2026Articles

On August 7, 2026, Anthropic added cross-session messaging to Claude Code 2.1.224. Claude can now discover other Claude Code sessions running separately and send the information they need as text messages.

I have used two approaches to parallel work: delegating parts of one job to subagents, and launching separate sessions so several jobs can run side by side. The second approach offers more freedom, but it also creates an annoying problem. When one session makes a decision, I have to explain that decision again in the other session. This new feature feels designed to reduce exactly that kind of human relay work.

This article explains what the feature changes, how it differs from subagents and agent teams, and how beginners can use it safely in real parallel workflows.

What can cross-session messaging do?

Cross-session messaging lets independent Claude Code sessions exchange short pieces of text when one session has information another needs. Behind the scenes, Claude Code uses ListAgents to discover reachable sessions and SendMessage to deliver a message. Users do not need to memorize those tool names. They can simply tell Claude what to ask or share in natural language.

Capability	Example use
Share a key update with another session	Pass along a specification change, research finding, or test result to related work
Ask another session a question	Check whether a long-running test or migration has finished and receive the answer in the current session
Let Claude send a proactive warning	Notify another session when a new change may affect what that session is building

If the receiving session is busy, it reads the message between tool calls without interrupting the tool currently running. If it is idle, the message starts a new turn. The receiving session can reply when needed, so questions and answers can travel in both directions.

The sessions share a written summary, not history or files

The most important limitation is that two sessions do not merge. Anthropic’s documentation says that the receiving session gets plain text written by Claude. It does not receive the sender’s conversation history or files.

For example, if one session changes an API specification, the other might receive a short report such as, “The new field is tenant_id, and the related tests have passed.” The full code change and the conversation that led to the decision are not copied automatically.

It is therefore better to think of this as handing a useful note to a coworker during a job, rather than moving an entire conversation into another session.

How is this different from subagents and agent teams?

These features can look similar, but cross-session messaging is primarily for independent sessions that the user started and has been steering separately.

Approach	Relationship	How information returns	Best suited to
Subagent	A worker delegated part of a job by a parent session	Returns its result to the parent	Research, tests, and focused review work
Separate session	An independent workspace started by the user	The user previously handled most handoffs; sessions can now exchange messages	Different goals, branches, models, or long-running jobs
Agent team	Multiple sessions managed together by a team lead	Coordinates through a shared task list and team messaging	Work that Claude should split, assign, and supervise

Subagents follow a hierarchy: the parent delegates a bounded task and collects the result. Separate sessions remain independent, and the user can choose a different direction for each one. Cross-session messaging keeps that independence while allowing only the necessary information to move between them.

The handoff problem I experienced with parallel sessions

I use subagents when I want to separate research or verification inside one larger job. I launch a separate session when I want a clearer division between goals, models, or working contexts.

Separate sessions make it possible to research an article in one place while editing a website in another. But when those jobs become related, I have had to copy and re-explain several pieces of context:

What the current session is trying to accomplish
Which files it changed
What has been decided and what remains unresolved
What the other session needs to check

If I omit that explanation, the other session may continue working from an outdated assumption. If I paste too much history, the useful information gets buried. Based on the announced behavior, cross-session messaging should reduce this coordination burden by letting Claude summarize the relevant point and send it to the appropriate session.

How to get started

Cross-session messaging requires Claude Code 2.1.224 or later. As of August 8, 2026, it is available on macOS and Linux, including Linux under WSL 2. It is not available on native Windows. It is also unavailable through certain external providers, including Amazon Bedrock.

Run claude --version and confirm that you have version 2.1.224 or later.
Start multiple Claude Code sessions. If helpful, use /rename to give each one a clear role.
Run /list-agents or /peers to confirm that the other session is reachable.
Tell Claude who should receive the information, or what you want it to ask.

For example:

Summarize the tenant_id change and the test results,
then send them to the session working on the payments API.

Ask the session running the migration in my other terminal
whether it has finished, and report the answer here.

You do not need to begin by learning every internal tool. Give each session a recognizable role and try one status question or one concise update first.

Messaging does not automatically resolve file conflicts

Easier communication does not remove the risk of two sessions editing the same file at the same time. If several sessions are working on one repository, separate their checkouts with Git worktrees or assign clear file ownership.

A useful handoff message can follow this five-part format:

Goal: What this session is trying to accomplish
Decision: What has now been decided
Changes: Files or specifications that changed
Open issue: What is still unresolved
Request: What the other session should do

A message from another session also does not count as the user’s approval. Actions that require permission still follow the receiving session’s own rules. A slash command included in another session’s message arrives as plain text and is not executed automatically.

This boundary may add a little friction, but it prevents communication between sessions from becoming an uncontrolled transfer of authority. Delivered messages also use tokens, so it is better to send a focused update when a decision or dependency changes than to stream every minor action.

I hope Codex adds coordination between independent tasks

As of August 8, 2026, the official Codex documentation describes delegation through subagents, parallel chats isolated with worktrees, and Handoff for moving a chat and its code between Local and Worktree. However, I could not find an equivalent documented user-facing feature that discovers an independently running task, sends it a summary, and returns its answer to the original task.

I use both subagent delegation and separate parallel tasks in Codex. For that reason, I hope Codex eventually adds a similar way for active tasks to exchange a short message only when they need to coordinate.

I am not looking for every conversation to be merged automatically. The useful version would let Codex find a related task by name, send a concise summary of a change, and return an answer to the task that asked the question. A proactive warning when two tasks are likely to touch the same file would make parallel work safer as well.

AI Jiten’s view: the real gain is lower coordination cost

The value of this update is not that the AI suddenly became more intelligent. It reduces the amount of time a person spends repeating context and carrying information between several AI sessions.

Parallel work does not become faster simply because more sessions are running. Separate jobs contribute to one result only when their boundaries, changes, and questions can be shared. Cross-session messaging is a foundation for treating several AI sessions not as isolated conversations, but as a small team that can communicate when necessary.

Summary

Claude Code’s cross-session messaging allows independent sessions to exchange the text they need and send questions and answers back and forth. It does not share conversation history or files, so it is not full synchronization. Even so, it should significantly reduce the work of re-explaining context during parallel tasks.

To try it, give two sessions clear names and start with one small request, such as asking for the status of another job. Continue to state file ownership and key decisions explicitly. A better communication channel helps, but people still need to define where one job ends and another begins.

Sources

Information was checked on August 8, 2026. Claude Code’s supported platforms, minimum version, provider requirements, and Codex features may change. The Codex comparison is based on the absence of an equivalent feature in the official documentation available on that date.