AGENTS.md

1---
2description: Development guidance for the @cline/llms package.
3globs: "src/**/*.ts,src/**/*.tsx,*.md"
4alwaysApply: true
5---
6 
7# @cline/llms Development Guidance
8 
9## Provider Option Routing
10 
11- `models.dev` catalog data and AI SDK provider behavior are the default
12  sources of truth for general model/provider support.
13- Do not build a broad Cline-maintained model capability or behavior registry.
14- `GatewayModelCapability` is semantic: what the model can do, not provider
15  quirks, default behavior, or wire-format details.
16- Stable, reliable known-model facts belong in typed `ModelInfo.metadata`
17  helpers or `src/providers/model-facts.ts`.
18- Stable provider routing facts belong in `GatewayProviderMetadata.routing`
19  and the relevant builtin provider manifest. For example, if a native
20  provider uses a known reasoning wire format for a model route, add a typed
21  `GatewayReasoningFormat` value and route metadata instead of matching that
22  provider id directly in a rule predicate.
23- Provider wire-format encoding belongs in `PROVIDER_OPTION_RULES` and codec
24  helpers under `src/providers/routing`.
25- Local or dynamic provider fallbacks, such as Ollama or routed model-id
26  heuristics, are allowed only as documented, narrowly scoped, tested
27  exceptions.
28- Fallback heuristics need negative or graceful-degradation tests, not only
29  happy-path tests.
30 
31When changing provider options, keep the split explicit:
32 
33```text
34request intent + model/provider facts -> named provider-option rule -> provider wire format
35```
36 
37If the same fact-resolution logic is needed across several providers, use a
38shared helper first. Add a new registry only after repeated logic proves the
39rule table and helpers are no longer enough.
40