Skip to content

Add OpenClaw + Plano intelligent routing demo#761

Merged
salmanap merged 10 commits intomainfrom
openclaw-routing-demo
Feb 17, 2026
Merged

Add OpenClaw + Plano intelligent routing demo#761
salmanap merged 10 commits intomainfrom
openclaw-routing-demo

Conversation

@adilhafeez
Copy link
Copy Markdown
Contributor

@adilhafeez adilhafeez commented Feb 17, 2026

Summary

  • Adds a new demo under demos/llm_routing/openclaw_routing/ showing Plano's preference-based routing powering OpenClaw (open-source personal AI assistant)
  • Routes conversational and agentic tasks to Kimi K2.5 (cost-effective) and code generation, testing, and complex reasoning to Claude
  • Includes config, docker-compose (Jaeger), run/test scripts, and full README with architecture diagram, demo scenarios, and cost analysis

adilhafeez and others added 9 commits February 17, 2026 03:16
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>
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>
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>
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>
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>
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>
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>
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>
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>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need this in the demo folder for OpenClaw. This would be useful in a general routing demo.


```bash
cd demos/llm_routing/openclaw_routing
planoai up --service plano --foreground
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets just make this planoai up (the simplest command)

docker logs plano 2>&1 | grep MODEL_RESOLUTION
```

### Jaeger Tracing (Optional)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would show our local terminal based tracing here for starters

Copy link
Copy Markdown
Contributor

@salmanap salmanap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make these minor modifications and push the demo in

@salmanap salmanap merged commit c69fbd8 into main Feb 17, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants