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

> ## Agent Instructions
> Start new users at /index, then /self-hosting to choose and prepare a host, including home networks at /homelab or infrastructure providers at /self-hosting/platforms. Continue through /first-task. Use Local development only when the user intends to modify Roomote itself.
> When an agent is asked to follow /self-hosting or install Roomote autonomously, read and follow /self-hosting/agent-installation as the normative automation contract even though it is intentionally hidden from side navigation.
> Use the one-command Linux installer for both evaluation and production. On macOS or Windows, create or reuse a full Ubuntu VM and run the same installer inside it; do not replace the installer with the repository's development Compose files.
> For a local VM, prepare a stable public HTTPS domain before connecting providers. Use a named tunnel with internal origin TLS or public DNS with ports 80/443 forwarded to the Linux host. Cloudflare Quick Tunnels do not support the Server-Sent Events Roomote uses; do not use them for the complete setup path.
> Run automated installs with --no-setup-url so the bootstrap token is not captured in the agent transcript. Let the user obtain the setup URL in a trusted terminal, enter credentials, and complete browser authorization.
> Proceed through safe, reversible setup and pause for privileged host or VM changes, public tunnel creation, credentials or browser authorization, durable external-account changes, destructive operations, existing-state conflicts, or when no documented safe default applies.
> A setup is not complete when the services merely start. Follow /first-task to verify sign-in, repository sync, and a real Roomote task that can clone and run a command. A saved environment is optional for a repository task. Verify branch or pull-request delivery and previews when configured; Slack and other communications providers are optional.

# Better Stack

> Bring monitoring and incident context into Roomote tasks.

Connect Better Stack when investigations depend on logs, incidents, uptime
signals, or other monitoring context that already lives there.

## When to use it

* Investigate a production issue with the monitoring context already attached
* Inspect uptime or incident signals before deciding what to fix next
* Give Roomote operational evidence without pasting screenshots or summaries
  into the prompt

## How setup works

Admins connect Better Stack once from the **Integrations** page.

## What to expect

Roomote uses Better Stack as task context for investigation and triage. Code
changes, validation, and review still happen through the normal Roomote task and
repository workflow.

## Recipes using this

* [Triage customer issues](https://docs.roomote.dev/cookbook/support-channel)


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