Advanced Routing Config #17

New Issue

Open

opened 2025-09-28 17:05:39 +02:00 by mpuchstein · 0 comments

mpuchstein commented

2025-09-28 17:05:39 +02:00

Owner

Configuration goals
- Centralize provider/model selection, task-phase policies, and guardrails so the agent can plan and route deterministically, with clear human overrides when needed.
- Support both static routing (simple rules) and dynamic routing (router decisions based on complexity/cost/latency), evolving from basic rules to learned strategies over time.
- Leverage MCP’s dynamic capability discovery to keep the inventory current without hardcoding server details or tool sets.
In-tool config UI
- Provider registry: list and enable/disable providers (e.g., Ollama local, cloud APIs), store keys safely outside prompt context, and annotate capabilities (code, long-context, function-calling).
- Model catalog: per provider, show models, context length, cost/latency class, eval tags, and allowed tools, sourced from provider APIs or a cached manifest.
- Profiles and policies: presets like “Local-only,” “Balanced,” “High-accuracy” with phase-specific routing (planner/executor/verifier) and budget ceilings per run.
- Constraints and guardrails: disallow network or certain tools for specific phases, enforce patch-only edits, and require human approval thresholds for large diffs.
- Observability: show chosen route, cost/latency estimates, and fallbacks taken to keep routing transparent and debuggable.

1. Configuration goals - Centralize provider/model selection, task-phase policies, and guardrails so the agent can plan and route deterministically, with clear human overrides when needed. - Support both static routing (simple rules) and dynamic routing (router decisions based on complexity/cost/latency), evolving from basic rules to learned strategies over time. - Leverage MCP’s dynamic capability discovery to keep the inventory current without hardcoding server details or tool sets. 1. In-tool config UI - Provider registry: list and enable/disable providers (e.g., Ollama local, cloud APIs), store keys safely outside prompt context, and annotate capabilities (code, long-context, function-calling). - Model catalog: per provider, show models, context length, cost/latency class, eval tags, and allowed tools, sourced from provider APIs or a cached manifest. - Profiles and policies: presets like “Local-only,” “Balanced,” “High-accuracy” with phase-specific routing (planner/executor/verifier) and budget ceilings per run. - Constraints and guardrails: disallow network or certain tools for specific phases, enforce patch-only edits, and require human approval thresholds for large diffs. - Observability: show chosen route, cost/latency estimates, and fallbacks taken to keep routing transparent and debuggable.

mpuchstein changed title from ~~[feat~~ to [feat] Advanced Routing Config

2025-09-28 17:05:55 +02:00

mpuchstein changed title from ~~[feat] Advanced Routing Config~~ to Advanced Routing Config

2025-09-28 17:08:58 +02:00

mpuchstein added the enhancement label 2025-09-28 17:09:08 +02:00

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Owlibou/owlen#17