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

# Kimi for Coding

> Connect a Kimi for Coding membership key and use its included coding models.

Kimi for Coding is Moonshot AI's membership-based coding service. Its keys use a
dedicated coding endpoint and are not interchangeable with Moonshot Open
Platform API keys.

## Get a membership key

Activate a Kimi for Coding membership, then create a key in the
[Kimi Code console](https://www.kimi.com/code/console). Use the separate
[Moonshot AI provider](/providers/inference/moonshot-ai) for keys created at
`platform.kimi.ai`.

## Configuration

Add **Kimi for Coding** in **Settings > Models** and paste the membership key,
or configure:

```sh theme={null}
KIMI_API_KEY=...
```

Roomote exposes supported models under the `kimi-for-coding/` prefix. The
recommended mappings can use Kimi's stronger model for coding, vision, planning,
and review while assigning its faster coding model to helper and explore work.

## Cost behavior

Requests consume the allowance included with the Kimi for Coding membership,
not a Moonshot Open Platform API balance. Roomote displays the provider-reported
usage window when the Kimi service returns it. Plan limits and renewal behavior
in the Kimi Code console are authoritative.

## Verify setup

1. save `KIMI_API_KEY`
2. confirm Kimi for Coding models appear in **Settings > Models**
3. apply a recommended mapping or assign one model manually
4. run a small task and confirm the membership usage display updates

## Common issues

* **The key is rejected.** Confirm it came from the Kimi Code console after
  membership activation, not the Moonshot Open Platform.
* **The allowance is exhausted.** Wait for the plan window to reset or change
  to a separately billed inference provider.
* **Usage is missing.** Kimi's usage endpoint can change or be unavailable;
  model requests may still work normally.