Back to Signal Feed
CodeTracked since May 19, 2026

Aider adds OrcaRouter as a first-class provider path

Aider introduces native OrcaRouter support (`orcarouter/` model prefixes) so users can invoke OrcaRouter-hosted models through existing aider flows with one provider-style key, instead of treating it as an external add-on path.

OrcaRouteraiderOrcaRouterModelManagerModelInfoManager

What Happened

  • Aider introduces native OrcaRouter support (`orcarouter/` model prefixes) so users can invoke OrcaRouter-hosted models through existing aider flows with one provider-style key, instead of treating it as an external add-on path.
  • Aider introduces native OrcaRouter support (`orcarouter/` model prefixes) so users can invoke OrcaRouter-hosted models through existing aider flows with one provider-style key, instead of treating it as an external add-on path.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Add a native OrcaRouter provider integration path in aider: new `OrcaRouterModelManager` loads and caches OrcaRouter model catalog data (max tokens, input/output costs), `ModelInfoManager` resolves `orcarouter/` model metadata when litellm lacks built-in details, and `Model.send_completion` routes calls through `api.orcarouter.ai` using `ORCAROUTER_API_KEY` while preserving aider’s existing alias and per-provider behavior.

Why Track This

Why It Matters

Aider users can now run a broad set of third-party models via one OrcaRouter entry (`orcarouter/<vendor>/<model>`) with consistent metadata and routing, which makes model experiments and provider switching in day-to-day workflows faster and less error-prone. The router implementation reuses aider’s existing OpenAI-compatible request path by rewriting to `openai/<rest>` for litellm and injecting OrcaRouter credentials/headers, so teams should watch pricing-feed availability and format changes, 24-hour cache drift, and any provider-side API/base-url incompatibilities that could cause wrong model selection or unexpected token-cost estimates.

Impact

Aider users can now run a broad set of third-party models via one OrcaRouter entry (`orcarouter/<vendor>/<model>`) with consistent metadata and routing, which makes model experiments and provider switching in day-to-day workflows faster and less error-prone. The router implementation reuses aider’s existing OpenAI-compatible request path by rewriting to `openai/<rest>` for litellm and injecting OrcaRouter credentials/headers, so teams should watch pricing-feed availability and format changes, 24-hour cache drift, and any provider-side API/base-url incompatibilities that could cause wrong model selection or unexpected token-cost estimates.

What To Watch Next

  • Watch whether OrcaRouter becomes a repeated pattern.
  • Track follow-up changes around Model Routing and Gateways.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: orcarouter_pricing_api_downtime, orcarouter_catalog_schema_change.
Open Topic TimelineOpen Technical EventOpen Original Sourceorcarouter_pricing_api_downtime / orcarouter_catalog_schema_change / cache_stale_pricing_24h / model_prefix_routing_regression / env_key_validation_edge_case

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

aider-ai/aider PR #5147: feat: add OrcaRouter (orcarouter/) as a first-class provider

PR #5147 adds OrcaRouter provider integration by wiring pricing/catalog metadata and completion routing so `orcarouter/<vendor>/<model>` calls are handled as an aider-native model source.