continuedev / continuedev/continue
Docs: configure ZvenoAI through the OpenAI-compatible provider
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Problem
ZvenoAI exposes an OpenAI-compatible endpoint, but Continue users currently have to infer the provider: openai configuration and the exact apiBase themselves.
Proposed scope
Add a short provider guide that:
- uses Continue's existing
openaiprovider rather than adding a runtime provider; - shows
https://api.zveno.ai/v1and one current model ID; - keeps the API key in a Continue secret;
- links to the live ZvenoAI model catalog instead of duplicating a model list or prices.
The public production /v1/models endpoint currently confirms the proposed model ID and tool-calling parameters. I can send the focused docs PR if this scope is welcome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Continue’s existing documentation for the openai provider and its secret configuration. Confirm the https://api.zveno.ai/v1 endpoint, select a current model from the live ZvenoAI model catalog, and finish when the guide covers the provider, endpoint, model, secret, and catalog link without adding a runtime provider.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100