01Connect sessions through the work#
Open the sessions you want to connect in split-view groups. They become available to one another automatically, even across groups that are not on screen. Ask one session to read another’s recent work, send it a message or delegate a task.
For example, ask your writing session to use the research session’s findings for a launch brief. The agent reads that session’s recent visible progress and uses it in its own work. A message sent to a peer appears in the receiving conversation with the sending session identified.
02See the connections in Agent map#
Open Agent map from the group bar. Each card shows a session number, provider, model and current status. Select a card to jump to that session.
Arrows show the direction of messages, and the number on a connection shows how many messages were exchanged. Reading a session alone does not create an arrow. This gives you a view of which agents have coordinated, alongside their current activity.
03Carry context across providers and devices#
The sessions can use different providers. They can also run on different connected hosts when both hosts support session bridging. Keep the web or desktop client open and connected to those hosts.
Shared context is recent visible conversation and activity. It does not merge the chats or synchronize their files. Cross-host messages appear in the receiving conversation; Agent map currently draws message arrows within each host.
Your agents can build on work already done, while each session remains a separate place to continue that part of the job.
Use another session without keeping its pane open#
Authorized sessions on the same computer can find, read and message one another without being in the same split view. Ask, for example: “Read the customer research session and use its findings to draft the handover.” Use the session’s title or tab number; include the computer if a number could refer to more than one session.
For sessions on different computers, keep one web or desktop client open and connected to both hosts. The sessions do not need open panes.
Closing a pane organizes your view; it does not revoke communication access. Workspace ownership and permissions still apply. Agent map shows sessions in open panes, so an absent card is not evidence that another session is inaccessible. A delivered message is not proof that its task is finished, and sharing context does not copy files between computers.
