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

# GitHub Copilot

> Use models included with an eligible GitHub Copilot account in Roomote.

GitHub Copilot gives Roomote access to supported models through a user's active
Copilot plan. This inference connection is independent of Roomote's [GitHub
source-control app](/providers/source-control/github).

## Connect GitHub Copilot

Add **GitHub Copilot** in **Settings > Models** and follow the GitHub device-code
flow. Sign in to a GitHub account with an active Copilot plan and approve the
connection. See [GitHub Copilot plans and setup](https://docs.github.com/en/copilot)
if the account does not have access yet.

No API key or environment variable is required. Roomote stores the OAuth record
and exposes supported models with the `github-copilot/` prefix.

## Cost behavior

Requests use the connected Copilot plan. For qualifying legacy annual Pro and
Pro+ plans, some models consume premium requests according to GitHub's
multipliers, and Roomote shows the remaining legacy quota when GitHub returns
it. Other current plans use GitHub AI Credits. GitHub billing and [Copilot plan
details](https://github.com/features/copilot/plans) are authoritative.

## Verify setup

1. complete the GitHub device-code flow
2. confirm GitHub Copilot shows as connected
3. enable a `github-copilot/...` model and assign it to a role
4. run a small task and check the plan-usage line when available

## Common issues

* **GitHub authorizes but Roomote reports no Copilot access.** Confirm the signed-in
  account has an active individual or organization-provided Copilot seat.
* **A model is unavailable.** Model availability and premium multipliers vary by
  plan; select another supported model or check the organization's Copilot policy.
* **The connection stops working.** Reconnect if GitHub revoked or expired the
  device authorization.