Wayfinder 0.1.1 - sharper console, one-step install
A polish release on top of v0.1.0: the operator console gets a branded redesign, the gateway and UI install in one step, and the docs make it clear where Wayfinder actually sits. No behavior, API, or config changes — drop-in over v0.1.0.
Installation
pip install -U "wayfinder-router[gateway]" # route traffic through the gateway
pip install -U "wayfinder-router[all]" # gateway + UI together (new)
pip install -U wayfinder-router # just the scorer + CLI + Python API
What's new
A branded console
wayfinder-router ui is no longer a generic form — it's a deliberate, modern surface: a teal-on-cream/navy palette, automatic light and dark (it follows your OS), a wordmark + tagline header, carded sections, a custom threshold slider, a recommendation pill, and refined tables and contribution bars. Same four tabs (Explain / Calibrate / Configure / Onboard), same behavior — just slick now.
One-step install for the full local experience
pip install "wayfinder-router[all]" brings up the gateway and the UI together, instead of adding the extras separately. The deterministic core stays zero-dependency; all is just a convenience aggregate of the existing extras.
Docs that explain where Wayfinder sits
A new "Where Wayfinder sits" section (with a diagram) makes the model explicit: Wayfinder is transparent middleware behind any OpenAI-compatible client — Open WebUI, LibreChat, an IDE assistant, your own app — and "local" vs "hosted" are backends, not separate UIs. Install guidance now leads with [gateway], the extra you need to actually route traffic.
Upgrade
Fully backward-compatible with v0.1.0 — no changes to the CLI, the gateway endpoints, the JSON contract, or wayfinder-router.toml. Just pip install -U.
Looking ahead: v0.2.0 and wayfinder-chat
Today Wayfinder is something you put behind your own client. Next, we want a version you can just open and chat with — routing built in, nothing to wire up.
wayfinder-chat will be a companion app: a fork of LibreChat (MIT) with the Wayfinder gateway inside, so a casual user installs one thing and gets —
- a real chat window, not a config form;
- routing controls in the settings — set the local-vs-cloud threshold and watch it take effect;
- a clear read on which model answered each message, and why.
It's a deliberate split, not a pivot: wayfinder-router stays the lean, deterministic, bring-your-own-client router for power users and production gateways, while wayfinder-chat is the turnkey, batteries-included path for everyone else — two products, used independently.
The direction is recorded in WF-ADR-0010, and it's still exploratory - no firm timeline yet - but that's where we're headed.