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

# Overview

> What you need to know.

Roomote works best when one person owns the initial setup, gets the first environment into good shape, and then helps the rest of the team see useful work land in the tools they already use.

This docs site is organized around that path: get the setup right, make the first task reviewable, then expand where Roomote shows up in your workflow.

<CardGroup cols={2}>
  <Card title="Get started" icon="rocket" href="/quickstart">
    Connect GitHub and Slack, create the first environment, and run the first
    task.
  </Card>

  <Card title="Roll out Roomote to your team" icon="users" href="/roll-out-roomote-to-your-team">
    Keep the first rollout small, visible, and easy to evaluate.
  </Card>

  <Card title="Dashboard and settings overview" icon="layout-dashboard" href="/dashboard-and-settings-overview">
    Learn where admins manage setup and where reviewers inspect task output.
  </Card>

  <Card title="Configure environments" icon="folder-tree" href="/environments">
    Give Roomote the repos, services, secrets, and guidance it needs to verify
    work.
  </Card>

  <Card title="Review a task" icon="list-checks" href="/tasks">
    Check the transcript, logs, diffs, previews, and follow-up path before
    anything ships.
  </Card>

  <Card title="What to ask Roomote" icon="sparkles" href="/use-cases">
    See the kinds of asks that stay scoped, useful, and reviewable.
  </Card>
</CardGroup>

## What Roomote is for

Roomote is not an IDE, local copilot, or desktop app. It is a shared engineering teammate that works from Slack, GitHub, Linear, and the web dashboard so your team can ask repo-grounded questions and create reviewable work without pulling everyone into the same editor session.

Roomote is especially useful for:

* answering codebase questions without pulling an engineer into the thread
* investigating bugs and flaky behavior
* planning changes before implementation
* handling chores, small fixes, and backlogged improvements
* reviewing PRs and following up on review feedback
* resolving merge conflicts and repository maintenance work
* producing visible, reviewable progress for the whole team

## The shortest path to a good first rollout

<Steps>
  <Step title="Connect GitHub and Slack">
    GitHub gives Roomote repository access and normal review paths. Slack gives
    your team the easiest shared surface for first tasks.
  </Step>

  <Step title="Create one environment that can actually prove work">
    Start with the repo or repo set you need for an early win. Include the
    services, secrets, ports, and guidance Roomote needs to run tests or open a
    preview.
  </Step>

  <Step title="Run a scoped first task">
    Start with something concrete: a bug investigation, a small fix, a plan, or
    a codebase question with clear repository context.
  </Step>

  <Step title="Review the task output">
    Using the provided screenshots, screencasts, preview URLs, or details from the task view in the web UI (transcript, logs, artifacts, etc).
  </Step>

  <Step title="Merge the change">
    Accept it into your codebase.
  </Step>

  <Step title="Do a little dance">
    You'll feel like it.
  </Step>
</Steps>

<Note>
  Roomote complements editor-based coding tools by making shared engineering
  work visible and reviewable outside the IDE.
</Note>

## Where to go next

If you are setting up Roomote for the first time, start with the [Quickstart](/quickstart). If you are planning a team rollout, read [Roll out Roomote to your team](/roll-out-roomote-to-your-team). If the setup is already running, move to [Configure environments](/environments), [Review a task](/tasks), or [Integrations overview](/integrations).