Skip to content

feat(client): recognize Novita as a compatible provider for error links - #227

Open
jax-novita wants to merge 1 commit into
Vizards:mainfrom
jax-novita:add-novita-provider-links
Open

feat(client): recognize Novita as a compatible provider for error links#227
jax-novita wants to merge 1 commit into
Vizards:mainfrom
jax-novita:add-novita-provider-links

Conversation

@jax-novita

Copy link
Copy Markdown

Summary

  • Recognize api.novita.ai as a known-compatible base URL alongside api.deepseek.com
  • Add Novita's API-key, usage, and status URLs to the provider-aware HTTP error action links (401/402/5xx)

Why

deepseek-copilot.baseUrl already lets users point this extension at any OpenAI-compatible endpoint, and Novita's /openai/v1 endpoint matches the SSE response shape this client parses (delta.content, delta.reasoning_content, usage). Users who set baseUrl to Novita currently fall back to the generic error message instead of getting a direct link to create a key, check usage, or check status the way DeepSeek users do.

Validation

  • npm run format:check
  • npm run compile
  • npm run lint
  • Verified against the live Novita API: GET /openai/v1/models (307 models, deepseek/deepseek-v4-pro active), non-streaming and streaming chat completions against deepseek/deepseek-v4-flash return the same field shape this client's DeepSeekClient parses (delta.reasoning_content, usage, [DONE])

The extension already supports pointing `deepseek-copilot.baseUrl` at
any OpenAI-compatible endpoint. Add Novita's API-key, usage, and status
URLs so users on `api.novita.ai` get the same provider-aware 401/402/5xx
action links DeepSeek users get, instead of falling back to the
generic message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant