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

# xAI Grok Subscription

> Connect an eligible SuperGrok or X Premium+ subscription to Roomote.

The xAI Grok subscription provider lets Roomote use included Grok capacity from
an eligible SuperGrok or X Premium+ account. It uses account authorization and
plan limits instead of an `XAI_API_KEY` and metered API billing.

## Connect a subscription

Add **xAI (Grok subscription)** in **Settings > Models** and complete the xAI
authorization flow with the account that owns the eligible plan. No API key or
deployment environment variable is required.

Subscription models keep the `xai/` prefix. When both subscription and [xAI API
key](/providers/inference/xai) connections exist, Roomote prefers subscription
access for those models.

## Cost behavior

Requests consume the plan's included usage windows rather than an xAI API
balance. Roomote displays plan and allowance information when xAI's unofficial
CLI usage service returns it. That service can change without notice, so the
usage line may disappear even while inference still works. Your xAI or X plan
and billing page is authoritative.

## Verify setup

1. complete the xAI authorization flow
2. confirm the Grok subscription shows as connected
3. enable an `xai/...` model and assign it to a role
4. run a small task and check the subscription usage display when available

## Common issues

* **Authorization succeeds but models fail.** Confirm the account has an
  eligible active plan with coding or API-compatible Grok access.
* **Usage is not displayed.** The provider's unofficial usage endpoint may be
  unavailable; try a task before reconnecting.
* **The allowance is exhausted.** Wait for the plan window to reset or disconnect
  the subscription so a configured `XAI_API_KEY` can provide metered capacity.