> ## 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
> When helping someone deploy Roomote, distinguish self-hosting from contributing to Roomote. Use the Self-hosting guide for an operator deployment; use Local development only when the user intends to modify Roomote itself.
> Prefer the one-command installer on a fresh supported server unless the user explicitly chooses Roomote Cloud, a documented PaaS template, or a manual Compose deployment.
> Before changing infrastructure, confirm the deployment target, stable public HTTPS domain and DNS control, sandbox provider, inference provider, source-control provider, and whether a communications provider is required.
> Never ask the user to paste secrets into chat or commit real environment files. Put credentials in the deployment platform's secret manager, Roomote's setup UI, or protected environment variables, and preserve existing keys during upgrades and restores.
> Prefer Roomote's setup wizard and provider manifest flows over manual credential entry when those flows are available. Ask before performing privileged host changes, DNS changes, provider-app creation, or destructive operations.
> A setup is not complete when the services merely start. Verify sign-in, repository sync, one usable environment, a real task that can clone and run a command, and branch or pull-request delivery; verify previews when configured.
> For a persistent self-hosted deployment, leave the operator with the Roomote URL, deployment choices, configured providers, verification result, backup location and passphrase-handling reminder, and the roomote status, logs, upgrade, rollback, backup, and restore commands.

# Fast sessions

> Chat with the fast orchestrator from the dashboard and review every Fast conversation's transcript.

Fast is Roomote's conversational orchestrator: it answers directly when it can
and delegates execution work into tasks when needed. A Fast session is one
persisted Fast conversation, whether it started in Slack, Discord, an
automation, or the web dashboard.

## Start a Fast session from the dashboard

On the home page, open the workspace selector next to the prompt box and choose
**Fast**. Your prompt starts a Fast session instead of a sandbox task, and
Roomote takes you straight to the session view, where the response streams in
as it is produced.

Use Fast when you want an answer, a decision, or a delegation rather than a
full sandbox run. Fast can still launch tasks on your behalf; delegated tasks
appear in the transcript with links to their task pages.

## The session view

A session's transcript shows prompts, replies, and the tool activity behind
them, rendered with the same transcript view as tasks, with a generated title
that updates as the conversation evolves. The view updates in real time while
a turn is running, so you can watch tool calls complete and replies land
without refreshing.

## Reply to a session

Every session has a reply box at the bottom of the transcript; follow-ups
continue the same conversation with full context. For conversations that live
on another surface, such as a Slack thread, Roomote's answer is posted back
into the originating thread with a quoted copy of your web message, so the
conversation stays in one place for everyone following it there. Fast replies
in Slack and Discord carry the same "Reply or use the web app" footer as task
replies, linking to the session view.