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

# Cloudflare

> Inspect and operate Cloudflare resources from Roomote tasks.

Connect Cloudflare when tasks need account, zone, DNS, Workers, security, or
other Cloudflare API context.

## How setup works

A deployment operator connects Cloudflare once from the **Integrations** page
using OAuth. Cloudflare uses dynamic client registration and asks the operator
to approve the permissions available to the shared deployment connection.

## Permissions and changes

Cloudflare exposes one tool for finding API operations and one tool for running
them. The same execution tool can call read and write APIs, so Roomote treats
mutations as explicit actions: it only changes Cloudflare resources when the
request clearly asks for that specific change. Cloudflare still enforces the
permissions granted during OAuth consent.

## Verify the connection

Start with a read-only request, such as listing zones or inspecting a Worker.
If the request is denied, reconnect Cloudflare and review the permissions made
available during consent.


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