Setup
- Install Continue in VS Code or a JetBrains IDE.
- Open Continue's config file (
config.yaml). - Add a model entry:
name: My Config
version: 1.0.0
schema: v1
models:
- name: luv13 GLM 5.3 Flash
provider: openai
model: luv13/glm-5.3-flash
apiBase: https://api.luv13.ai/v1
apiKey: <YOUR_LUV13_API_KEY>
roles:
- chat
- edit
- apply- Replace
<YOUR_LUV13_API_KEY>with your key, save, and pick the model in Continue's model menu.
Don't commit this file with a real key in it. See API Key Best Practices.
Useful options
Continue's config reference lists more fields you can add to a model:
defaultCompletionOptionswithtemperature,maxTokens,topPandstop. Whether luv13 honors each one is covered on Request Parameters.capabilitieswithtool_useto tell Continue the model can call tools, which agent mode needs.requestOptionswithtimeoutandheaders.
Why not autocomplete
Tab autocomplete works differently from chat, and Continue's docs include a setting (useLegacyCompletionsEndpoint) for models that should use the older /completions endpoint. luv13 serves POST /v1/chat/completions and returns 404 for /v1/completions. See Endpoints. The safe setup is luv13 for chat and edits, and a separate model for autocomplete.
Check your settings first
curl https://api.luv13.ai/v1/chat/completions \
-H "Authorization: Bearer $LUV13_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "luv13/glm-5.3-flash", "messages": [{"role": "user", "content": "Hi"}]}'