Patrick Wozniak 0700d9b61d fix(core): register the custom api in the pi-ai compat registry ...

pi routes the main chat through the registered provider, but sibling
extensions that call streamSimple from @earendil-works/pi-ai/compat with
the active Command Code model resolve model.api through the compat
api-registry, which only knows built-in APIs. On plain pi that failed
with "No API provider registered for api: commandcode-custom".

Register commandcode-custom there and delegate to the transport router.
The registry resolves no credentials for extension providers, so fall
back to the configured Command Code key when the caller passes none.

Closes #68

(cherry picked from commit 7e9659e672771c6a9223b95938e50fb2a051a0a7)

2026-09-01 23:29:30 +02:00

..

advisory-injector-extension.ts

test(omp): cover developer advisory delivery

2026-08-17 09:04:32 +02:00

commandcode-model-ids.json

fix(pricing): refresh catalog pricing snapshot

2026-09-01 23:29:16 +02:00

commandcode-pricing.json

fix(pricing): refresh catalog pricing snapshot

2026-09-01 23:29:16 +02:00

compat-caller-extension.ts

fix(core): register the custom api in the pi-ai compat registry

2026-09-01 23:29:30 +02:00