Skip to content

[Docs] Clarify when Kenari model discovery connects - #50

Draft
zoomote[bot] wants to merge 1 commit into
mainfrom
fix/scope-provider-model-requests-3somxbbf7yubt
Draft

[Docs] Clarify when Kenari model discovery connects#50
zoomote[bot] wants to merge 1 commit into
mainfrom
fix/scope-provider-model-requests-3somxbbf7yubt

Conversation

@zoomote

@zoomote zoomote Bot commented Aug 28, 2026

Copy link
Copy Markdown

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

The Kenari provider guide now states that Zoo Code fetches the public model catalog when the user selects Kenari, not when another provider is selected. It also discloses that the direct request exposes standard connection metadata such as the user's IP address and does not include workspace content.

Why this change was made

Users monitoring extension traffic could see an unexpected connection to kenari.id without context. This documentation accompanies Zoo-Code issue #1424 and the provider-scoping fix.

Impact

Users can understand exactly when the Kenari model-catalog connection occurs and what information is sent. There is no documentation route or navigation change.

Screenshots

Kenari model discovery disclosure

The rendered Kenari documentation explains that model discovery occurs on Kenari selection, does not occur for other providers, and sends no workspace content.

Related PRs

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