Skip to content

feat(ai): add Neuralwatt provider - #1051

Open
sk0x0y wants to merge 5 commits into
code-yeongyu:mainfrom
sk0x0y:feat/provider-neuralwatt
Open

feat(ai): add Neuralwatt provider#1051
sk0x0y wants to merge 5 commits into
code-yeongyu:mainfrom
sk0x0y:feat/provider-neuralwatt

Conversation

@sk0x0y

@sk0x0y sk0x0y commented Aug 20, 2026

Copy link
Copy Markdown

Summary

Add Neuralwatt (https://api.neuralwatt.com/v1, env NEURALWATT_API_KEY) as a built-in OpenAI-completions provider with a 22-model static catalog generated from packages/ai/scripts/generate-models.ts. Includes provider factory, registration, env-key mapping, unit + key-gated cross-provider tests, and coding-agent/infra mirror updates.

Why this belongs in core

Built-in provider catalogs and env-key detection live in packages/ai core; a per-user models.json overlay cannot register a builtin catalog provider or contribute to KnownProvider / builtinProviders / env-api-keys. Adding Neuralwatt as a core provider lets users configure only an API key.

Verification

  • npm run check green
  • CI=1 npm test green (13732 passed / 929 skipped / 0 failed)
  • npm run check:model-data green
  • Live-API compat probe used only to confirm conservative default flags (no secrets in repo)

Compatibility

Purely additive; no existing provider modified. The only generated manifest update is for the new neuralwatt.json catalog.


Summary by cubic

Adds Neuralwatt as a built-in OpenAI-completions provider with a 22-model catalog at https://api.neuralwatt.com/v1. Users previously needed per-user overlays to reach it; now setting NEURALWATT_API_KEY is enough.

  • Registers the provider in packages/ai core: KnownProvider, builtinProviders(), env-key map, and generated model data.
  • Adds the neuralwatt default model kimi-k2.6-fast and display name to the coding agent.
  • Covers docs, --help, devcontainer, and test-script env lists.
  • Adds key-gated live tests for streaming, tools, reasoning, images, Unicode, tokens, context overflow, and cross-provider handoff, plus a catalog test.

Rollout

  • Additive; no existing providers changed.
  • Set NEURALWATT_API_KEY to use; live tests only run when it's present.
  • Generated artifacts are up to date; regenerate to resolve manifest conflicts after syncing upstream.

Written for commit 7994183. Summary will update on new commits.

Review in cubic

Add Neuralwatt (https://api.neuralwatt.com/v1, env NEURALWATT_API_KEY) as a
built-in OpenAI-completions provider with a 22-model static catalog.

- catalog source of truth in packages/ai/scripts/generate-models.ts
- provider factory, env key mapping, KnownProvider union, builtin registration
- unit + key-gated cross-provider tests
- coding-agent + infra mirror updates (docs, env lists, devcontainer, test scripts)
sk0x0y and others added 3 commits August 21, 2026 18:57
Run npm run hydrate-model-data so data/.manifest.json carries the
neuralwatt.json sha256 + structureHash, per the providers AGENTS.md
generation contract (data/ is committed generated source; validate
with npm run check:model-data — passing).
@sk0x0y

sk0x0y commented Aug 27, 2026

Copy link
Copy Markdown
Author

Synced with latest main (333f8b6, changelog-only conflicts resolved keeping both sides) and regenerated the model data artifacts (79941836) so data/.manifest.json carries the neuralwatt entry — npm run check:model-data passes.

For context since the original submission: Neuralwatt's model entries are now tracked in models.dev (anomalyco/models.dev#5561 — includes DeepSeek V4 Pro, Qwen 3.8 27B, V4 Flash Flex), so the generated catalog stays current with the upstream data source. I've also proposed the provider upstream (earendil-works/pi#8749) with a port of this implementation.

Happy to restructure anything if there's a preferred convention for provider additions.

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