> ## 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.
> 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 without a stable public domain, create a temporary HTTPS tunnel, pass its hostname to the installer with internal origin TLS, and keep the tunnel running for OAuth callbacks and webhooks. Quick Tunnel hostnames are temporary and do not provide wildcard preview routing.
> 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. Verify sign-in, repository sync, one usable environment, and a real Roomote task that can clone and run a command; verify branch or pull-request delivery and previews when configured.

# DeepSeek

> Use DeepSeek's direct API for Roomote tasks and sessions.

DeepSeek exposes its current Flash and Pro models through an OpenAI-compatible
API. Roomote connects to that API directly rather than routing requests through
another inference provider.

## Get an API key

Create a key in the [DeepSeek platform](https://platform.deepseek.com/api_keys)
and add balance to the account that will run Roomote tasks.

## Configuration

Add **DeepSeek** in **Settings > Models** and paste the key, or configure:

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

Roomote recommends these direct model routes:

* `deepseek/deepseek-v4-pro` for coding, code review, and planning
* `deepseek/deepseek-flash` for helper, explore, and vision work

The Flash model accepts text and image input. The Pro model accepts text input.
Both models support tool calls and configurable reasoning.

## Cost behavior

DeepSeek charges the connected account for input, cached input, and output
tokens. Roomote records usage and estimates cost from current model metadata;
DeepSeek's [models and pricing](https://api-docs.deepseek.com/quick_start/pricing)
page remains authoritative.

## Verify setup

1. save `DEEPSEEK_API_KEY`
2. confirm DeepSeek V4.1 Flash and DeepSeek V4 Pro 0813 appear in **Settings > Models**
3. confirm the desired models and role mapping are enabled
4. run a small task and confirm the request appears in DeepSeek platform usage

## Common issues

* **Authentication or balance errors occur.** Confirm the key is active and the
  account has enough balance.
* **A model ID is rejected.** Use the exact `deepseek/...` ID shown in Roomote;
  OpenRouter and other provider routes are separate connections.
* **Image input fails on Pro.** Assign `deepseek/deepseek-flash` to the vision
  role; the Pro model is text-only.