Skip to content

DocsCoding agents

Continue CLI

Run the Continue CLI (cn) on your own Osarai GPU with a local config.yaml and the key kept in Continue's secrets file.

The Continue CLI (cn) is Continue's coding agent for the terminal. It reads the same config.yaml as the Continue editor extensions and talks to Osarai over Chat Completions.

The Continue CLI answering on qwen3.8-27b served by Osarai
Continue CLI running on an Osarai instance.

Install

Terminal
npm install -g @continuedev/cli

The package installs the cn command.

Configure

Add the model

~/.continue/config.yaml
name: Osarai
version: 1.0.0
schema: v1
models:
  - name: Qwen3.8 27B (Osarai)
    provider: openai
    model: qwen3.8-27b
    apiBase: https://osarai.xyz/v1
    apiKey: ${{ secrets.OSARAI_API_KEY }}
    roles:
      - chat
      - edit
      - apply
    capabilities:
      - tool_use
    defaultCompletionOptions:
      contextLength: 131072
      maxTokens: 16384

Store the key

~/.continue/.env
OSARAI_API_KEY=qck_your_key_here
  • ${{ secrets.OSARAI_API_KEY }} is filled in from ~/.continue/.env, so config.yaml holds no secret.
  • capabilities: [tool_use] tells Continue the model calls tools; without it the agent cannot read or edit files.
  • contextLength is the real context window, so Continue trims history in time.

Run

Terminal
cd your-project
cn --config ~/.continue/config.yaml

Pass --config for interactive sessions: without it, the first start offers to set up an Anthropic key instead of reading your file. An alias saves typing:

Terminal
alias cn='cn --config ~/.continue/config.yaml'

To run one prompt and print the answer:

Terminal
cn -p "Explain what src/math.ts does"

cn asks before it runs tools that change things. --readonly starts in plan mode with read-only tools; --auto allows every tool, so use it only in a sandbox.

Troubleshooting

SymptomFix
To get started, enter your Anthropic API keyPress Ctrl+C and start cn with --config ~/.continue/config.yaml
cn hangs or asks you to sign in to ContinueIt did not find ~/.continue/config.yaml; check the path or pass --config
ENOENT … config.yamlThe file passed to --config does not exist
401OSARAI_API_KEY is missing from ~/.continue/.env, or the name differs from the one in secrets.
The model never calls toolsAdd capabilities: [tool_use] and use a model with tool calls (qwen3.8-27b)
503 … not ready yetThe instance is still starting; wait for Ready on the instance page