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

# Surfaces

> One Sidekick across web, desktop, Slack, and Teams, with the same thread ledger on every surface.

Sidekick meets people where they already work. It is one product, not four separate ones, and the thread is the same ledger no matter which surface you open it from.

## One product, four surfaces

<Columns cols={2}>
  <Card title="Web" icon="globe">
    The full Sidekick application in the browser. Everything a thread holds is here.
  </Card>

  <Card title="Desktop app" icon="laptop">
    Sidekick as an installed app. It adds on-your-computer execution and nudges.
  </Card>

  <Card title="Slack" icon="hash">
    Start and continue threads from Slack, inside the conversations already happening there.
  </Card>

  <Card title="Teams" icon="video">
    The same in Microsoft Teams: work with Sidekick without leaving the tool your team uses.
  </Card>
</Columns>

## The thread is the same ledger everywhere

A thread started in Slack is the same thread you can open on the web. The conversation, tool runs, approvals, files, and artifacts do not fork per surface. You pick up the work wherever you are, and the record stays whole.

## What the desktop app adds

The desktop app is the surface that unlocks two capabilities the others do not:

* **On-your-computer execution**: run a thread's work on your approved device instead of the cloud. See [How work runs](/docs/sidekick/concepts/how-work-runs).
* **Nudges**: prompts that bring relevant work back to you at the right moment.

<Note>
  Slack and Teams are entry points into the same threads, not separate copies. Governance, models, and placement behave the same way regardless of which surface you started from.
</Note>

## Where to go next

<CardGroup cols={2}>
  <Card title="Sidekick in Slack and Teams" icon="slack" href="/docs/sidekick/use/slack-teams">
    How to start and continue threads from chat.
  </Card>

  <Card title="Running on your computer" icon="laptop" href="/docs/sidekick/use/on-your-computer">
    How the desktop app runs work on your own device.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Slack surface" icon="settings" href="/docs/sidekick/admin/slack">
    How admins set up and govern the Slack surface.
  </Card>

  <Card title="Teams surface" icon="settings" href="/docs/sidekick/admin/teams">
    How admins set up and govern the Teams surface.
  </Card>
</CardGroup>