> ## 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.

# Cookbook

> Copyable recipes for turning Roomote automations, skills, and integrations into standing team systems.

Roomote's abilities go way beyond ad hoc prompt → PR interactions. With integrations and automations, you can put many of your team's workflows on autopilot, from investigation to resolution and beyond.

This cookbook collects proven recipes to help you boost your team's productivity
and the quality of your output.

| Recipe                                                                         | Use to                                                                                                 |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| [Draft product updates](/cookbook/product-updates-newsletter)                  | Turn recent product work into a customer-ready draft                                                   |
| [Ease your team into cloud agents](/cookbook/ease-your-team-into-cloud-agents) | Build trust in Roomote through small, visible, low-risk team habits.                                   |
| [Evaluate outage impact](/cookbook/vendor-outage-triage)                       | Filter vendor status noise by comparing each incident with your real code, regions, and feature usage. |
| [Fix CI failures](/cookbook/ci-failure-auto-fix)                               | Keep the build green by having Roomote verify and fix CI breakages automatically.                      |
| [Schedule maintenance](/cookbook/scheduled-housekeeping)                       | Turn flaky-test scans, feature-flag audits, and dependency reviews into recurring Roomote work.        |
| [Triage customer issues](/cookbook/support-channel)                            | Give support escalations a repeatable path through production evidence, data, and code.                |

## Contribute a recipe

Have a Roomote workflow other teams could reuse? Start with
[contributing recipes](/cookbook/template), fill in every section, and open a
[Cookbook recipe issue](https://github.com/RooCodeInc/Roomote/issues/new?template=cookbook-recipe.yml)
on the Roomote repository.