Add OpenPaths provider

[lee101]

What

Adds OpenPaths as a provider. OpenPaths is an OpenAI-compatible LLM gateway (similar in shape to OpenRouter): a single base URL fronts many models.

• Base URL: https://openpaths.io/v1
• Models: https://openpaths.io/v1/models
• API key env: OPENPATHS_API_KEY (key page: https://openpaths.io/account)
• Default model: openpaths/auto

Changes

Minimal, additive — mirrors the existing declarative OpenAI-compatible profile entries (baseten, deepseek, fireworks, etc.):

• packages/llm/src/providers/openai-compatible-profile.ts: add openpaths: { provider: "openpaths", baseURL: "https://openpaths.io/v1" } to the profiles map.
• packages/llm/src/providers/openai-compatible.ts: add export const openpaths = define(profiles.openpaths) family helper.

No dedicated AI SDK plugin is needed: OpenPaths is a plain OpenAI-compatible gateway and is served by the existing generic openai-compatible plugin, exactly like the other profile-only providers (baseten/deepseek/fireworks). The per-provider plugins under packages/core/src/plugin/provider/ exist only for providers that ship a dedicated @ai-sdk/* package, which does not apply here.

Testing

• bun run typecheck (tsgo --noEmit) in packages/llm — passes.
• bun test test/exports.test.ts test/provider/openai-compatible-chat.test.ts — 9 pass, 0 fail.
• Full monorepo install was not run end-to-end: bun install aborts on an unrelated native build (tree-sitter-powershell / node-gyp) in this environment; verification was scoped to the llm package with --ignore-scripts.

Note

This LLM engine (@opencode-ai/llm) is shared with opencode. If maintainers would prefer this profile entry land upstream there first, happy to redirect the PR.

🤖 Generated with Claude Code

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• packages/llm/src/providers/openai-compatible-profile.ts
• packages/llm/src/providers/openai-compatible.ts

Other Observations (not in diff)

File	Issue
N/A	Changeset missing — Adding a new LLM provider is user-facing. Consider adding a .changeset/openpaths-provider.md with "kilo-code": minor.
packages/llm/test/provider/openai-compatible-chat.test.ts	Test coverage gap — The providerFamilies array on line 43 tests model construction for each family provider. openpaths is not added there; consider adding it to keep coverage parity with other profile-only providers like deepseek/fireworks/baseten.

Fix these issues in Kilo Cloud

---

_{Reviewed by deepseek-v4-pro · 508,510 tokens}

_{Review guidance: REVIEW.md from base branch main}

[chrarnoldus]

from our testing it seems this pull request does not actually add the provider to the selection in the CLI, extension, etc. Feel free to reopen with screenshots if this is resolved.

Additionally, it is recommended to submit the provider for inclusion in https://github.com/anomalyco/models.dev first.

[lee101]

Thanks, that direction makes sense. I opened a models.dev submission for OpenPaths first:

anomalyco/models.dev#2958

It adds the OpenAI-compatible base URL and the documented OpenPaths router aliases, with bun validate passing locally. Once that lands, I can refresh the Kilo provider PR with the provider selection/test coverage and screenshots you asked for.