> ## Documentation Index
> Fetch the complete documentation index at: https://alike.help/llms.txt
> Use this file to discover all available pages before exploring further.

# Run parallel sessions

> Let your own agent sessions see each other and send each other messages, across agents.

You can run several agents at the same time. For example: a refactor in Claude Code, a client update in Codex, and a test fix in Cursor. Each session knows only its own window. With Alike, your sessions can see each other and send each other messages. You do not have to copy text between terminals.

## See your other sessions

When a session starts, the brief lists the other live sessions on the same work item. You can also ask your agent:

> Which of my other agent sessions are live right now?

The agent lists your live sessions, with the agent, the branch, the title, and the last activity of each one. The list also shows teammates' sessions that are shared with you. You can see those sessions, but you cannot send them a message.

Each session is also an item in Alike, of type `agent_session`. Your agent can find a session by its title and read its summary and linked work items, the same way it reads a task. A teammate's session appears when their sharing level includes sessions. See [Who sees what](https://alike.help/privacy/who-sees-what.md).

## Send a message to another session

Ask your agent in normal words:

> Tell my Codex session on the api repository that I renamed `OrderStatus` to `CheckoutStatus` in the shared types.

A message has one of three types:

| Type | Use it to | Reply expected? |
| - | - | - |
| `tell` | Share information | No |
| `ask` | Ask a question | Yes |
| `propose` | Suggest a change to an item, for example a task's status | Yes |

The message arrives at the other session's next turn. When the other session gets an ask or a proposal, it can continue for one more turn to answer. See [When Alike adds context](https://alike.help/use/in-your-agent.md#when-alike-adds-context).

## Reply to a message

The receiving agent replies with one of these words:

| Message type | Possible replies |
| - | - |
| `ask` | `answer`, `counter`, or `decline` |
| `propose` | `accept`, `counter`, or `decline` |

The reply goes back to the sending session at its next turn.

> [!NOTE]
>
> Messages between your own sessions need no confirmation, because they stay in your account. A message to another person is different. Your agent must ask you first. See [Work with teammates](https://alike.help/use/teammates.md).

## Tips

* **Link sessions to the same work item.** When two sessions work on the same branch or pull request, each one sees the other in its brief.
* **Refer to items, not descriptions.** Ask the agent to include the ID of the task or decision. The other session then knows exactly which item you mean.
* **Use asks only when you need an answer.** An ask expects a reply, so it can make the other session take one more turn.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.