Continue

Continue is an AI assistant that runs inside VS Code and JetBrains IDEs. It reads OpenAI-compatible models from its config, so it's a first-class connect target: the proxy writes one entry per network model for you.

Before you start

Do the shared setup from How-to guides first: the proxy must be running (zs-proxy proxy start) and funded (zs-proxy fund).

The quick way: zs-proxy connect continue

zs-proxy connect continue                          # add the proxy's models to Continue
zs-proxy connect continue --model qwen3-coder      # ...limit it to a single model
zs-proxy connect continue --print                  # preview the merged config, write nothing

This adds an entry per network model to the models list in your existing ~/.continue/config.yaml (backing the original up to config.yaml.bak). Your own models are left untouched, and re-running is idempotent — it replaces its own zerosignal/… entries rather than duplicating them. What each entry looks like:

models:
  - name: zerosignal/qwen3-coder
    provider: openai
    model: qwen3-coder
    apiBase: http://127.0.0.1:9376/v1
    apiKey: zerosignal-local        # placeholder — the proxy ignores it
    roles: [chat, edit, apply]
    capabilities: [tool_use]        # + image_input when the model accepts images

info

Each entry is named zerosignal/<id> so you can tell the network models apart in Continue's picker. Continue's YAML merge doesn't preserve comments, so a written config.yaml comes back without any you'd added by hand — the backup keeps the original.

Select the model and run

Reload the Continue extension (or restart the IDE) so it picks up the new config, then choose a zerosignal/… model from Continue's model dropdown and send a message. The first reply confirms the whole path — encrypt, pay, route — is working.

Troubleshooting

Symptom	Fix
connect says Continue wasn't detected	Name it explicitly — zs-proxy connect continue configures the named tool even without detection, writing ~/.continue/config.yaml.
New models don't appear	Reload the Continue extension or restart the IDE so it re-reads ~/.continue/config.yaml.
Continue isn't using the proxy	Pick a zerosignal/<model> from the model dropdown, and confirm those entries exist under models in the config.
Connection refused / can't reach the endpoint	The proxy isn't running or the base URL is wrong. Confirm with curl http://localhost:9376/healthz and start it with zs-proxy proxy start.
wallet_unfunded / payment errors	Add funds with zs-proxy fund — see Wallet & funding.

What's next

• Connecting AI tools — every connect flag and the other supported tools.
• Routing preferences — pin an operator or set a price ceiling.
• Pricing — what an agent turn costs.
• How-to guides — connect another app.