pi-team v0.6.11
This patch release makes model fallback channel-aware without changing the public tool API or requiring configuration migration.
Highlights
- Same model, another channel first — pi-team now treats
model.idas the model identity andprovideras the access channel. If a worker fails, an untried provider offering the same model ID is preferred before switching to a different model. - Channel-aware candidate selection — automatic fallback candidates reserve available slots for the primary model ID through other configured providers, so equivalent channels are not displaced by ordinary metadata ranking.
- Bounded fallback remains intact — each fallback key is attempted at most once. After all channels for the requested model are exhausted, retry continues in the original fallback order and terminates when the candidate list is exhausted.
- No provider-wide guess from one failure — a failure from one
provider/modelpair does not mark every model exposed by that provider as unavailable.
Compatibility
- No tool schema or configuration changes
- No migration required
- Built-in roles and playbooks remain model-neutral
- Compatible with the existing Pi and Oh My Pi extension entry points
Validation
- 318 automated tests across 9 test files
- File-size, model-neutral default-resource, TypeScript, and test gates pass
- Post-reload DeepSeek worker smoke succeeded on
deepseek/deepseek-v4-flash - Runtime fallback smoke completed in two bounded attempts:
openai-codex/gpt-5.3-codex-sparkreturned no assistant output, thenopenai-codex/gpt-5.4succeeded - Published tarball contents remain limited to
src/, the bilingual READMEs,LICENSE, and package metadata
Upgrade
Pi
pi install npm:pi-team@0.6.11Then run /reload.
Oh My Pi
omp install pi-team@0.6.11Restart or reload Oh My Pi after installation.