Back to Signal Feed
CodeTracked since May 19, 2026

Aider adds OrcaRouter as a first-class LLM provider

The PR introduces a native OrcaRouter integration in aider under the `orcarouter/` namespace, including model metadata lookup and request routing so users can call OrcaRouter models from the same aider workflow. It also wires token-limit and cost metadata from OrcaRouter into aider’s model info path with cached retrieval, and exposes startup validation for the new API key.

OrcaRouteraiderOrcaRouterModelManagerModelInfoManager

What Happened

  • The PR introduces a native OrcaRouter integration in aider under the `orcarouter/` namespace, including model metadata lookup and request routing so users can call OrcaRouter models from the same aider workflow. It also wires token-limit and cost metadata from OrcaRouter into aider’s model info path with cached retrieval, and exposes startup validation for the new API key.
  • The PR introduces a native OrcaRouter integration in aider under the `orcarouter/` namespace, including model metadata lookup and request routing so users can call OrcaRouter models from the same aider workflow. It also wires token-limit and cost metadata from OrcaRouter into aider’s model info path with cached retrieval, and exposes startup validation for the new API key.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Added a first-class OrcaRouter provider path in aider by implementing `OrcaRouterModelManager` for fetching and caching OrcaRouter model limits/costs, delegating `orcarouter/` model info resolution to it in `ModelInfoManager`, and routing `orcarouter/<vendor>/<model>` requests through the existing OpenAI-compatible litellm client with injected OrcaRouter API key and attribution headers.

Why Track This

Why It Matters

Developers and operators using aider can now consume OrcaRouter’s catalog from the same command-line flow with one provider-specific setup key, which lowers integration friction when adding/switching vendor models and enables broader model experimentation without custom client changes; the follow-up risk is that stale or wrong cached model metadata could produce unexpected quota ceilings or billing mismatches for production prompts. The implementation maps `orcarouter/` requests to the OpenAI-compatible endpoint used by litellm, adds a 24-hour on-disk cache for pricing and token limits, and adds startup validation plus an `orcarouter-auto` alias and docs/tests to make adoption safer.

Impact

Developers and operators using aider can now consume OrcaRouter’s catalog from the same command-line flow with one provider-specific setup key, which lowers integration friction when adding/switching vendor models and enables broader model experimentation without custom client changes; the follow-up risk is that stale or wrong cached model metadata could produce unexpected quota ceilings or billing mismatches for production prompts. The implementation maps `orcarouter/` requests to the OpenAI-compatible endpoint used by litellm, adds a 24-hour on-disk cache for pricing and token limits, and adds startup validation plus an `orcarouter-auto` alias and docs/tests to make adoption safer.

What To Watch Next

  • Watch whether OrcaRouter becomes a repeated pattern.
  • Track follow-up changes around LLMOps.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: model_metadata_cache_staleness, pricing_formula_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourcemodel_metadata_cache_staleness / pricing_formula_regression / orcarouter_prefix_routing_mismatch / api_key_or_header_missing_on_deployments

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

Aider now supports `orcarouter/<vendor>/<model>` models via `ORCAROUTER_API_KEY`, with pricing/catalog info loaded from OrcaRouter and cached in `~/.aider/caches/orcarouter_models.json`.