Phaseo CLI can create a local Continue configuration shared by the IDE extensions and the cn command-line interface.
Set up Continue
When ~/.continue/config.yaml and ~/.continue/.env are unused, setup creates both files:
The key is stored as PHASEO_API_KEY in ~/.continue/.env. useResponsesApi: false keeps requests on Phaseo’s Chat Completions path.
Continue’s global .env is plaintext. Never commit it. IDE extensions do not inherit ordinary shell environment variables, so the CLI uses Continue’s documented secret file.
PHASEO_API_KEY=<dedicated key> to the existing .env. Retrieve the key with phaseo integrations credential continue.
Verify
In VS Code or JetBrains, reload the window, open Continue, select Phaseo, and ask it to reply with PHASEO_CONTINUE_OK.
For Continue CLI, run cn. Use /config if another saved configuration is active, then send the same test prompt. Confirm the request appears in Phaseo activity.
Remove
Removal revokes the key and deletes both files only when they still carry the Phaseo CLI ownership marker. Manually merged entries are left untouched.
Troubleshooting
Phaseo does not appear
Reload the IDE and check that config.yaml includes the required top-level name, version, and schema fields.
Continue reports a missing secret
Confirm ~/.continue/.env contains the key returned by phaseo integrations credential continue, then restart the IDE.
Continue calls the Responses API
Keep useResponsesApi: false on the Phaseo model entry.
