Skip to main content
Run phaseo continue to write a Continue config that points at Phaseo, or add the same model entry and secret to your existing config. The IDE extensions and the cn CLI share the config.

​
Set up with the Phaseo CLI

If ~/.continue/config.yaml and ~/.continue/.env don’t exist, setup creates a Phaseo CLI: Continue API Key (90-day expiry, $100 monthly spend limit) and writes both files. Without --model, it uses anthropic/claude-sonnet-4.6.
~/.continue/config.yaml
The key goes in ~/.continue/.env as PHASEO_API_KEY. useResponsesApi: false keeps Continue on Phaseo’s Chat Completions endpoint.
Continue’s global .env is plaintext. Never commit it. IDE extensions don’t inherit shell environment variables, which is why the CLI uses Continue’s local secrets file.

​
Configure Continue manually

If either file already has your own settings, setup stops without changing it. Add the model entry above to your config.yaml, and add PHASEO_API_KEY=<key> to your .env, using phaseo integrations credential continue or any Phaseo API key. See Continue’s OpenAI provider docs for the other fields.

​
Check it works

In VS Code or JetBrains, reload the window, open Continue, select Phaseo, and ask it to reply with PHASEO_CONTINUE_OK. In the CLI, run cn (use /config if another config is active) and send the same prompt. Confirm the request appears in Settings → Usage → Logs.

​
Remove Phaseo

This revokes the key and deletes both files only if they still start with the Phaseo CLI marker. Entries you merged yourself are left alone.

​
Fix common problems

​
Phaseo doesn’t appear

Reload the IDE and check that config.yaml has the top-level name, version, and schema fields.

​
Continue reports a missing secret

Check that ~/.continue/.env has the key from phaseo integrations credential continue, then restart the IDE.

​
Continue calls the Responses API

Keep useResponsesApi: false on the Phaseo model entry.
Last modified on November 5, 2026