Add Novita AI as a provider option - #4133
Open
jax-novita wants to merge 2 commits into
Open
Conversation
Novita AI is an OpenAI-compatible inference endpoint (https://api.novita.ai/v3/openai), so it slots into the existing provider=openai path the same way vLLM, llama.cpp, Ollama, and Block Gateway already do — no new Provider enum variant needed. Adds it to the README's provider diagram and endpoint table, and to the is_openai_host host matrix test alongside OpenRouter and Block Gateway. Signed-off-by: jax-novita <jax-novita@users.noreply.github.com>
…nt documented endpoint The is_openai_host_matrix test case used https://api.novita.ai/v3/openai. That path still resolves today, but Novita's current documentation (novita.ai/docs/guides/llm-api) no longer shows it; the current documented OpenAI-compatible endpoint is https://api.novita.ai/openai. Verified live 2026-08-01: both paths return identical /models and /chat/completions results, and both are non-openai.com hosts so the test's expected boolean (false) is unchanged either way -- this corrects the literal, not the assertion. README.md's provider table and topology diagram do not mention any base URL literal for Novita, so no change needed there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
Compared against the baseline on
f3e5e812677f: compared_to_baseline. Pre-existing failures are left as-is.Reviewer Notes
cargo test -p buzz-agent --lib config::passing (121/121, from the original submission) demonstrates no regression, not that a live request against Novita's endpoint was exercised. This revision was made in an environment without a Rust toolchain, so it was not re-tested; the change is a single string literal swap in a test's input data, and the assertion's expected boolean is unaffected either way (neither URL is an*.openai.comhost), but that is an inference, not a verified result.config::unit test module was run (on the original submission), not the full crate, workspace, or desktop (pnpm test/tsc/biome) test suites — the sandbox's Rust toolchain build directory ran out of disk space untilCARGO_TARGET_DIRwas redirected to a separate volume, so wider verification (integration tests, desktop typecheck) was not attempted, then or in this revision.Providerenum variant or touch the desktopPERSONA_LLM_PROVIDER_OPTIONSdropdown — Novita AI is exposed only via the existingprovider=openai+OPENAI_COMPAT_BASE_URLpath, matching the most similar recent precedent (docs(buzz-agent): add OrcaRouter as a supported OpenAI-compatible provider #3096, OrcaRouter). A reviewer may prefer first-class UI treatment instead, or none at all.https://api.novita.ai/v3/openai, an older path that Novita's current documentation (novita.ai/docs/guides/llm-api) no longer shows; the currently documented endpoint ishttps://api.novita.ai/openai. Both paths return identical, working results today (verified against/modelsand/chat/completions), and the test's expected boolean is unchanged either way — so this was a stale citation rather than a functional break, but if your own testing shows Novita's API surface has moved again since 2026-08-01, please treat your own verification as authoritative over this PR's claim.