# Continue

> The VS Code and JetBrains assistant, and its `cn` CLI.

Source: https://www.lyber.ai/docs/agents/coding-agents/continue/ · Markdown: https://www.lyber.ai/docs/md/agents/coding-agents/continue.md

## Easy setup

Copy this prompt into Continue itself or any coding agent you use, such as Claude Code, Codex or Cursor. It adds Lyber to Continue's settings, keeps your key out of every file, and checks the connection without spending credit.

```text
Set up Continue on this computer to use Lyber, an OpenAI-compatible API.

Lyber:
- Base URL: https://lyber-paid-acceptance-gateway-production.up.railway.app/v1
- Models: minimax-m3.1-flash-abliterated (default; 1,048,576-token context, 32,768-token output) and deepseek-v4.1-flash-1017-abliterated (1,048,576-token context, 262,144-token output)
- API key: in the LYBER_API_KEY environment variable. Never print it, never write it into a file, and never ask me to paste it into this chat.

Do this:
1. Open ~/.continue/config.yaml. If it exists, copy it to ~/.continue/config.yaml.bak first, then merge these settings into it and keep everything else. If it doesn't exist, create it with exactly this:

name: Lyber
version: 1.0.0
schema: v1
models:
  - name: MiniMax M3.1 Flash (Lyber)
    provider: openai
    model: minimax-m3.1-flash-abliterated
    apiBase: https://lyber-paid-acceptance-gateway-production.up.railway.app/v1
    apiKey: ${{ secrets.LYBER_API_KEY }}
    roles: [chat, edit, apply]
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 32768
  - name: DeepSeek V4.1 Flash 1017 (Lyber)
    provider: openai
    model: deepseek-v4.1-flash-1017-abliterated
    apiBase: https://lyber-paid-acceptance-gateway-production.up.railway.app/v1
    apiKey: ${{ secrets.LYBER_API_KEY }}
    roles: [chat, edit, apply]
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 32768

2. If Continue isn't installed, tell me to run: npm install -g @continuedev/cli
3. If LYBER_API_KEY isn't set in my shell, tell me to add export LYBER_API_KEY="…" to my shell profile myself and open a new terminal.
4. Check the key without spending credit. This should print 200:
curl -s -o /dev/null -w "%{http_code}\n" https://lyber-paid-acceptance-gateway-production.up.railway.app/v1/models -H "Authorization: Bearer $LYBER_API_KEY"
5. Tell me what you changed and how to start Continue on Lyber: cn
Don't send a chat request through Lyber unless I ask.
```

## Manual setup

### 1. Install Continue

```bash
npm install -g @continuedev/cli
```

### 2. Put your key in your environment

Add this to your shell profile (`~/.zshrc` or `~/.bashrc`) and open a new terminal.

```bash
export LYBER_API_KEY="lyber_prepaid_…"
```

### 3. Add Lyber to `~/.continue/config.yaml`

Keep any settings already in the file; add these beside them.

```yaml
name: Lyber
version: 1.0.0
schema: v1
models:
  - name: MiniMax M3.1 Flash (Lyber)
    provider: openai
    model: minimax-m3.1-flash-abliterated
    apiBase: https://lyber-paid-acceptance-gateway-production.up.railway.app/v1
    apiKey: ${{ secrets.LYBER_API_KEY }}
    roles: [chat, edit, apply]
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 32768
  - name: DeepSeek V4.1 Flash 1017 (Lyber)
    provider: openai
    model: deepseek-v4.1-flash-1017-abliterated
    apiBase: https://lyber-paid-acceptance-gateway-production.up.railway.app/v1
    apiKey: ${{ secrets.LYBER_API_KEY }}
    roles: [chat, edit, apply]
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 32768
```

### 4. Start Continue

```bash
cn
```

## Notes

- The CLI and the extension share `~/.continue/config.yaml`. In the extension, pick the model from the model menu.
- `${{ secrets.LYBER_API_KEY }}` comes from your environment. An editor opened from the Dock may not see your shell's variables: start it from a terminal, or put `LYBER_API_KEY=…` in `~/.continue/.env`.
- Leave out `capabilities: [tool_use]`: with it, the extension adds `parallel_tool_calls` to every request with tools, which Lyber rejects. Continue still uses tools without it.
- The DeepSeek entry caps replies at 32,768 tokens to keep each request's credit hold small; raise `maxTokens` up to 262,144 if you need longer output.