How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

release - Prompt - OpenSmartRoute

Prompt file imported from corwinm/oil.code (.github/prompts/release.prompt.md). Copyright stays with the author.

Use the GitHub Actions Release workflow for automated releases instead of editing files and tagging manually.

Release workflow:

Ensure the commits on main follow conventional commit prefixes such as feat:, fix:, refactor:, perf:, or BREAKING CHANGE.
Open GitHub Actions and run the Release workflow.
Optionally set dry_run to true to preview the next version without publishing.
On a normal run, the workflow will:
- determine the next semantic version from commits on main
- update package.json
- update CHANGELOG.md
- create the release commit and tag
- create the GitHub Release with notes
- attach the packaged .vsix
- publish to the VS Code Marketplace and Open VSX

Release rules:

feat triggers a minor release.
fix, perf, refactor, and revert trigger a patch release.
docs, style, chore, test, build, and ci do not trigger a release.
Breaking changes trigger a major release.

Do not manually edit CHANGELOG.md, bump package.json, create tags, or run gh release create for standard releases.

Use the GitHub Actions Release workflow for automated releases instead of editing files and tagging manually. Release workflow: 1. Ensure the commits on `main` follow conventional commit prefixes such as `feat:`, `fix:`, `refactor:`, `perf:`, or `BREAKING CHANGE`. 2. Open GitHub Actions and run the `Release` workflow. 3. Optionally set `dry_run` to `true` to preview the next version without publishing. 4. On a normal run, the workflow will: - determine the next semantic version from commits on `main` - update `package.json` - update `CHANGELOG.md` - create the release commit and tag - create the GitHub Release with notes - attach the packaged `.vsix` - publish to the VS Code Marketplace and Open VSX Release rules: - `feat` triggers a minor release. - `fix`, `perf`, `refactor`, and `revert` trigger a patch release. - `docs`, `style`, `chore`, `test`, `build`, and `ci` do not trigger a release. - Breaking changes trigger a major release. Do not manually edit `CHANGELOG.md`, bump `package.json`, create tags, or run `gh release create` for standard releases.

Install release and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

release

About

Use it

Install release and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews