Model Routing
Paddles separates the planner and synthesizer into distinct roles, each routable to a different model. This lets operators match each workload to the smallest model that excels at it.
Two Roles
| Role | What it does | Optimized for |
|---|---|---|
| Planner | Recursive investigation: search, read, refine, branch | Tool use, multi-step reasoning, evidence gathering |
| Synthesizer | Final answer from evidence bundle | Answer quality, grounding, citation |
By default, both roles use the same model. The --planner-model flag overrides the planner independently.
Current Model Lanes
| Model | Role | Notes |
|---|---|---|
qwen-1.5b | Default synthesizer and planner | Lightweight, fast inference |
qwen3.5-2b | Opt-in planner or synthesizer | Heavier, better multi-step reasoning |
qwen-coder-0.5b/1.5b/3b | Coding-oriented variants | Optimized for code-heavy workloads |
sift-direct | Gatherer backend | Direct local retrieval for search/refine actions |
context-1 | Experimental boundary | Specialized planner/gatherer, fail-closed until ready |
Search Contract Parameters
search and refine planner actions share a gatherer contract that controls
retrieval depth and strategy:
mode:linearorgraphstrategy:lexical(BM25) orhybrid(BM25 + vector + RRF)step_limit: per-call retrieve budgetmax_items/max_snippet_chars/max_summary_chars: evidence bundle capsretained_artifact_limit: number of retained artifacts preserved for planner trace
Current defaults are documented on the Search and Retrieval page.
Multi-Provider Support
Paddles supports multiple HTTP API providers alongside local models:
- OpenAI-compatible APIs
- Anthropic API
- Gemini API
Each provider is accessed through the same synthesizer or planner contract. Credentials are managed per-provider through the TUI login flow or environment variables.
Routing In Practice
A lightweight synthesizer with a heavier planner:
paddles --model qwen-1.5b --planner-model qwen3.5-2b
A remote synthesizer with a local planner:
paddles --model kimi-k2.6 --planner-model qwen3.5-2b
The harness degrades gracefully — if a remote provider is unavailable, the turn fails closed with a clear error rather than producing an ungrounded answer.
What To Read Next
- Turn Loop — where routing fits in the overall cycle
- Recursive Planning — what the planner model actually does