# Continue

Configure Continue's IDE or CLI agent to use Laminarity through Chat Completions.

> Verification: source-checked; checked 2026-09-01; Continue YAML configuration — Prepared as second-wave coverage; client execution certification is pending.

## Store the key

Put `LAMINARITY_API_KEY` in a workspace `.env`, `.continue/.env`, or the global `~/.continue/.env`. Continue IDE extensions do not necessarily inherit variables exported by your shell.

## Configure the model

Set `useResponsesApi: false` so GPT-family names do not make Continue switch to the Responses endpoint. Laminarity's Chat Completions path is the broadest agent and tool compatibility surface.

```yaml
name: Laminarity
version: 1.0.0
schema: v1

models:
  - name: Laminarity Auto
    provider: openai
    model: auto
    apiBase: https://api.laminarity.ai/v1
    apiKey: ${{ secrets.LAMINARITY_API_KEY }}
    useResponsesApi: false
    roles:
      - chat
      - edit
      - apply
```

## Model selection

Use `auto` for routing and fallback. Duplicate the model entry with a concrete id from `/v1/models` only when a role must pin one model. Do not configure Continue autocomplete against Laminarity until a completion/FIM endpoint is available.

## Upstream documentation

- [Continue OpenAI-compatible providers](https://docs.continue.dev/customize/model-providers/top-level/openai)
- [Continue secret configuration](https://docs.continue.dev/faqs)