apunkt/plano
1
0
Fork 0
mirror of https://github.com/katanemo/plano.git synced 2026-05-08 07:12:42 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
plano/demos/llm_routing/openclaw_routing/config.yaml

32 lines
1,021 B
YAML
Raw Normal View History

Add OpenClaw + Plano intelligent routing demo (#761) * Add OpenClaw + Plano intelligent routing demo Demonstrates preference-based routing for personal AI assistants: Kimi K2.5 handles conversation and agentic tasks, Claude handles code generation, testing, and complex reasoning — with zero application code changes and ~48% cost savings. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove redundant provider_interface from Kimi K2.5 config The openai/ prefix in the model name already sets the provider interface. Setting provider_interface explicitly conflicts with it and fails config validation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Simplify config to v0.3.0 format, remove explicit Arch-Router entry Arch-Router is implicit when routing_preferences are defined. Aligns with the preference_based_routing demo pattern. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clean up Ollama/Arch-Router references, make Jaeger optional Router is handled internally by Plano — no need for Ollama or explicit Arch-Router setup. Jaeger is kept as an optional step in the README for developers who want tracing visibility. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove run_demo.sh, use planoai CLI directly The planoai CLI already handles startup. README now uses planoai up/down directly instead of a wrapper script. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove docker-compose.yaml, use inline docker run for Jaeger No need for a compose file when Jaeger is the only optional service. A single docker run command in the README is simpler. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clarify testing: OpenClaw channels vs direct Plano requests Primary testing is through messaging channels (Telegram, Slack, etc.) with log monitoring. The test_routing.sh script is now documented as an optional direct verification tool. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add OpenClaw onboarding instructions to README Includes install, onboarding wizard, channel setup, doctor check, and how to point the gateway at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use OpenClaw onboarding wizard for Plano provider setup Replace manual JSON config with instructions to use the openclaw onboard wizard to set up a custom OpenAI-compatible provider pointing at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fixed readme and removed unnecessary testing.sh file --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Salman Paracha <salmanparacha@MacBook-Pro-342.local>
2026-02-17 06:34:54 -08:00
version: v0.1.0
Unified overrides for custom router and orchestrator models (#820) * support configurable orchestrator model via orchestration config section * add self-hosting docs and demo for Plano-Orchestrator * list all Plano-Orchestrator model variants in docs * use overrides for custom routing and orchestration model * update docs * update orchestrator model name * rename arch provider to plano, use llm_routing_model and agent_orchestration_model * regenerate rendered config reference
2026-03-15 09:36:11 -07:00
overrides:
llm_routing_model: Arch-Router
Add OpenClaw + Plano intelligent routing demo (#761) * Add OpenClaw + Plano intelligent routing demo Demonstrates preference-based routing for personal AI assistants: Kimi K2.5 handles conversation and agentic tasks, Claude handles code generation, testing, and complex reasoning — with zero application code changes and ~48% cost savings. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove redundant provider_interface from Kimi K2.5 config The openai/ prefix in the model name already sets the provider interface. Setting provider_interface explicitly conflicts with it and fails config validation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Simplify config to v0.3.0 format, remove explicit Arch-Router entry Arch-Router is implicit when routing_preferences are defined. Aligns with the preference_based_routing demo pattern. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clean up Ollama/Arch-Router references, make Jaeger optional Router is handled internally by Plano — no need for Ollama or explicit Arch-Router setup. Jaeger is kept as an optional step in the README for developers who want tracing visibility. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove run_demo.sh, use planoai CLI directly The planoai CLI already handles startup. README now uses planoai up/down directly instead of a wrapper script. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove docker-compose.yaml, use inline docker run for Jaeger No need for a compose file when Jaeger is the only optional service. A single docker run command in the README is simpler. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clarify testing: OpenClaw channels vs direct Plano requests Primary testing is through messaging channels (Telegram, Slack, etc.) with log monitoring. The test_routing.sh script is now documented as an optional direct verification tool. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add OpenClaw onboarding instructions to README Includes install, onboarding wizard, channel setup, doctor check, and how to point the gateway at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use OpenClaw onboarding wizard for Plano provider setup Replace manual JSON config with instructions to use the openclaw onboard wizard to set up a custom OpenAI-compatible provider pointing at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fixed readme and removed unnecessary testing.sh file --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Salman Paracha <salmanparacha@MacBook-Pro-342.local>
2026-02-17 06:34:54 -08:00
listeners:
egress_traffic:
address: 0.0.0.0
port: 12000
message_format: openai
timeout: 30s
llm_providers:
# Kimi K2.5 — Moonshot AI's open model (1T MoE, 32B active params)
# Great for general conversation, agentic tasks, and multimodal work
# OpenAI-compatible API at $0.60/M input, $2.50/M output tokens
- model: openai/kimi-k2.5
access_key: $MOONSHOT_API_KEY
base_url: https://api.moonshot.ai/v1
default: true
routing_preferences:
docs: Fix incorrect routing preferences in OpenClaw demo config (#765)
2026-02-18 01:15:46 -08:00
- name: general conversation
description: general chat, greetings, casual conversation, Q&A, and everyday questions
Add OpenClaw + Plano intelligent routing demo (#761) * Add OpenClaw + Plano intelligent routing demo Demonstrates preference-based routing for personal AI assistants: Kimi K2.5 handles conversation and agentic tasks, Claude handles code generation, testing, and complex reasoning — with zero application code changes and ~48% cost savings. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove redundant provider_interface from Kimi K2.5 config The openai/ prefix in the model name already sets the provider interface. Setting provider_interface explicitly conflicts with it and fails config validation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Simplify config to v0.3.0 format, remove explicit Arch-Router entry Arch-Router is implicit when routing_preferences are defined. Aligns with the preference_based_routing demo pattern. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clean up Ollama/Arch-Router references, make Jaeger optional Router is handled internally by Plano — no need for Ollama or explicit Arch-Router setup. Jaeger is kept as an optional step in the README for developers who want tracing visibility. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove run_demo.sh, use planoai CLI directly The planoai CLI already handles startup. README now uses planoai up/down directly instead of a wrapper script. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Remove docker-compose.yaml, use inline docker run for Jaeger No need for a compose file when Jaeger is the only optional service. A single docker run command in the README is simpler. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Clarify testing: OpenClaw channels vs direct Plano requests Primary testing is through messaging channels (Telegram, Slack, etc.) with log monitoring. The test_routing.sh script is now documented as an optional direct verification tool. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add OpenClaw onboarding instructions to README Includes install, onboarding wizard, channel setup, doctor check, and how to point the gateway at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use OpenClaw onboarding wizard for Plano provider setup Replace manual JSON config with instructions to use the openclaw onboard wizard to set up a custom OpenAI-compatible provider pointing at Plano. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fixed readme and removed unnecessary testing.sh file --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Salman Paracha <salmanparacha@MacBook-Pro-342.local>
2026-02-17 06:34:54 -08:00
# Claude — Anthropic's most capable model
# Best for complex reasoning, code, tool use, and evaluation
- model: anthropic/claude-sonnet-4-5
access_key: $ANTHROPIC_API_KEY
routing_preferences:
docs: Fix incorrect routing preferences in OpenClaw demo config (#765)
2026-02-18 01:15:46 -08:00
- name: code generation
description: generating code, writing scripts, implementing functions, and building tool integrations
Reference in a new issue Copy permalink