Files
OmniRoute/docs
Diego Rodrigues de Sa e Souza 87c53cabac feat(api): add first-class Ollama local provider card (#5578)
Ollama is the most popular local runtime, yet OmniRoute only shipped
`ollama-cloud` (api-key, hosted) and `ollama-search` (web search) — there
was no dedicated card for the local Ollama chat runtime at localhost:11434,
so users had to fall back to the generic `openai-compatible-*` provider.

Add `ollama-local` to the local catalog:
- LOCAL_PROVIDERS entry (default http://localhost:11434/v1, no API key,
  passthroughModels → lists models via the OpenAI-compatible /v1/models)
- classify it as a self-hosted chat provider (SELF_HOSTED_CHAT_PROVIDER_IDS)
- route it through the local-baseUrl case group in DefaultExecutor.buildUrl
  so an empty baseUrl falls back to localhost:11434 instead of OpenAI
  (same fix class as llama-cpp #3136/#3197)
- bump the provider-count slice of PROVIDER_REFERENCE.md (236 → 237) and
  sync the count in README / AGENTS / CLAUDE

Tests: tests/unit/ollama-local-provider.test.ts (catalog shape, local
classification, and buildUrl routing — incl. the no-baseUrl OpenAI-fallback
regression guard).

Refs #5578
2026-06-30 23:43:27 -03:00
..
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00
2026-06-30 06:54:29 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00
2026-06-17 19:26:32 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00

title, version, lastUpdated
title version lastUpdated
OmniRoute Documentation 3.8.40 2026-06-28

OmniRoute Documentation

Navigable index of the OmniRoute documentation set. Topics are grouped by intent so you can find what you need quickly.

Looking for the project overview, install steps, or release notes? See the root README.md, CHANGELOG.md, and CONTRIBUTING.md.


For Non-Tech Users

Simple guides for using OmniRoute — no technical background needed.

getting-started/

guides/


For Tech Users

Technical documentation for developers and contributors.

architecture/

How the system is put together — read these to understand the runtime, code layout, and resilience model.

reference/

Lookup material — API surface, environment variables, CLI flags, provider catalog.

frameworks/

Pluggable subsystems exposed to clients, agents, and operators.

routing/

Combo routing, scoring, and replay.

security/

Guardrails, compliance, stealth, and the mandatory patterns for handling public credentials and error messages.

compression/

Prompt compression engines, rules, and language packs.

providers/

Provider-specific integration guides.

comparison/

ops/

Release, deployment, proxies, tunnels, coverage, database, monitoring.

diagrams/

Mermaid sources and exported SVG/PNG diagrams referenced from the docs above. See diagrams/README.md.

i18n/

Translated mirrors of the documentation in 42 locales. See i18n/README.md for the supported language list.

screenshots/

Static screenshots used by the dashboard and the README. Not part of the doc body.


Auto-generated artifacts

  • reference/PROVIDER_REFERENCE.md is generated by scripts/docs/gen-provider-reference.ts from src/shared/constants/providers.ts. Do not edit by hand.
  • The /docs UI is backed by Fumadocs MDX source generation from the subfolders above.