From 48989eba76f26dcd79f0512a331893d939c06716 Mon Sep 17 00:00:00 2001 From: Adil Hafeez Date: Tue, 17 Feb 2026 04:46:26 -0800 Subject: [PATCH] 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 --- demos/llm_routing/openclaw_routing/README.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/demos/llm_routing/openclaw_routing/README.md b/demos/llm_routing/openclaw_routing/README.md index 9e8cee2b..be1cdaa0 100644 --- a/demos/llm_routing/openclaw_routing/README.md +++ b/demos/llm_routing/openclaw_routing/README.md @@ -23,7 +23,7 @@ Plano uses a [preference-aligned router](https://arxiv.org/abs/2506.16655) to an - **Plano CLI**: `uv tool install planoai` or `pip install planoai` - **OpenClaw**: `npm install -g openclaw@latest` - **API keys**: - - `MOONSHOT_API_KEY` — from [Moonshot AI](https://platform.moonshot.cn/) + - `MOONSHOT_API_KEY` — from [Moonshot AI](https://www..moonshot.ai/) - `ANTHROPIC_API_KEY` — from [Anthropic](https://console.anthropic.com/) ## Quick Start @@ -61,17 +61,17 @@ Then run: openclaw onboard --install-daemon ``` -### 4. Test Routing +### 4. Test Routing Through OpenClaw -Run the test script to verify routing decisions: +Send messages through any connected channel (WhatsApp, Telegram, Slack, etc.) and watch routing decisions in a separate terminal: ```bash -bash test_routing.sh +planoai logs --service plano | grep MODEL_RESOLUTION ``` -## Demo Scenarios +Try these messages to see routing in action: -| # | Message | Expected Route | Why | +| # | Message (via your messaging channel) | Expected Route | Why | |---|---------|---------------|-----| | 1 | "Hey, what's up? Tell me something interesting." | **Kimi K2.5** | General conversation — cheap and fast | | 2 | "Remind me tomorrow at 9am and ping Slack about the deploy" | **Kimi K2.5** | Agentic multi-step task orchestration | @@ -81,6 +81,14 @@ bash test_routing.sh OpenClaw's code doesn't change at all. It points at `http://127.0.0.1:12000/v1` instead of a direct provider URL. Plano's router analyzes each prompt and picks the right backend. +### Verify Plano Routing Directly (Optional) + +To test Plano's routing without OpenClaw, run the test script which sends requests directly to the gateway: + +```bash +bash test_routing.sh +``` + ## Monitoring ### Routing Decisions