Skip to content

fix: register 'codebuddy-sdk' in pi-ai's apiProviderRegistry - #8

Closed
SoyWater wants to merge 1 commit into
RealAlexandreAI:masterfrom
SoyWater:master
Closed

fix: register 'codebuddy-sdk' in pi-ai's apiProviderRegistry#8
SoyWater wants to merge 1 commit into
RealAlexandreAI:masterfrom
SoyWater:master

Conversation

@SoyWater

@SoyWater SoyWater commented Sep 7, 2026

Copy link
Copy Markdown

pi.registerProvider alone only routes model-runtime-mediated streaming. Consumers that call pi‘s raw stream/streamSimple (e.g. pi-observational-memory's observer/reflector/dropper agents) bypass the model runtime and failed with 'No API provider registered for api: codebuddy-sdk', crashing the whole process because pi-agent-core's agentLoop has no rejection handler.

Registering the api id in pi's registry makes codebuddy models dispatchable from every entry point.

pi.registerProvider alone only routes model-runtime-mediated streaming.
Consumers that call pi-ai's raw stream/streamSimple (e.g.
pi-observational-memory's observer/reflector/dropper agents) bypass the
model runtime and failed with 'No API provider registered for api:
codebuddy-sdk', crashing the whole process because pi-agent-core's
agentLoop has no rejection handler.

Registering the api id in pi-ai's registry — the same registry builtin
apis live in — makes codebuddy models dispatchable from every entry
point. Idempotent and a no-op on pi versions without the export.
@SoyWater SoyWater closed this Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant