Show HN: Preference-aware routing for OpenClaw via Plano

Hey HN!

OpenClaw is notorious about its token usage, and for many the price of Opus 4.6 can be cost prohibitive for personal projects. The usual workaround is “just switch to a cheaper model” (Kimi k2.5, etc.), but then you are accepting a trade off: you either eat a noticeable drop in quality or you end up constantly swapping models back and forth based on usage patterns

I packaged Arch-Router (used by HF: https://x.com/ClementDelangue/status/1979256873669849195) into Plano and now calls from OpenClaw can get automatically routed to the right upstream LLM based on preferences you set. Preference could be anything that you can encapsulate as a task. For e.g. for daily calendar and email work you could redirect calls to k2.5 and for building apps with OpenClaw you could redirect that traffic to Opus 4.6

This hard choice of choosing one model over another goes away with this release.