---
title: "Multiplayer sessions"
description: "Every session is shared, so teammates can jump in and work alongside you and Indent."
---

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

# Multiplayer sessions

A session isn't a private thread between you and Indent — it's a shared workspace teammates can step
into and work in alongside you.

Indent knows who's on your team. Wherever you tag it, it joins with the full context of the task, so
a teammate who jumps in doesn't have to catch it up.

## Join from web, Slack, or GitHub

- **Web** — Open a session at [app.indent.com](https://app.indent.com) and a teammate can view it
  and add messages. Everyone sees the same history and the same live work.
- **Slack** — Anyone in a channel can mention `@indent` in the same thread and take part. The thread
  is the session; each person's messages land in the shared context. See
  [Working with Indent in Slack](/collaborating/working-in-slack).
- **GitHub** — A pull-request review is a session too. Anyone can reply in the comments to steer the
  work, and Indent responds with the full history of the review. See
  [Reviewing pull requests](/working-with-indent/reviewing-pull-requests).

> **Note**
>
> Private sessions are the exception: a direct message with Indent, a desktop local session, or a
> session you've made private stays with you. See [Personal integrations and private
> sessions](/collaborating/personal-and-private).

Source: https://docs.indent.com/collaborating/multiplayer/index.mdx