[FEATURE]:Inter session communication #52297

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Feature request: Inter-session chat and agent aliases

It would be useful to have a way for one session to communicate with another session.

For example:

Tell Agent A to explain the commit it just made.

The idea would be to introduce a persistent session alias or agent identifier, such as:

• Agent A
• Agent B
• Agent C

Then another session could reference that agent directly and ask it questions about its work, context, decisions, commits, or current task.

Current workaround

Today, I manually rename my sessions so I can identify what each one is doing.

I also prefix the session name with something like:

A - Implement authentication

B - Refactor API client

C - Add integration tests

This lets me manually find the session that corresponds to "Agent A", but there is no native way for another session to communicate with it.

Proposed feature

Add a session-level feature or flag that assigns a stable agent alias to a session.

For example:

agent: A

Then commands could work like:

Ask Agent A why it changed this function.

Tell Agent B to review Agent A's commit.

Ask Agent A for a summary of what it implemented.

Tell Agent C to continue from Agent B's findings.

The target agent should receive the request with access to its existing session context.

Example workflow

Imagine three sessions working on the same application:

A - Authentication

B - Frontend login page

C - Tests

From Session B, I could say:

Ask Agent A what API contract it implemented for login.

Then:

Tell Agent C to add tests based on Agent A's implementation.

Or:

Ask Agent B to explain the UI decisions it made in the latest commit.

This would avoid manually opening each session, copying context, and pasting it into another one.

Why this would be useful

OpenCode already works very well for running multiple parallel sessions.

The missing piece is coordination between those sessions.

With stable agent aliases and inter-session messaging, multiple OpenCode sessions could work more like a small team instead of completely isolated agents.

Thanks for building OpenCode. I use it heavily, and this would significantly improve multi-agent workflows.