feat(oauth): add logo_uri to client ID metadata documents - #10727
Merged
Conversation
Authorization servers that support the OAuth Client ID Metadata Document spec can display the client logo on consent screens. Points at the square black goose mark already served from goose-docs.ai, which renders on the light backgrounds consent screens typically use.
Abhijay007
approved these changes
Jul 29, 2026
alexhancock
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
logo_urito both client ID metadata documents (CIMD) served from goose-docs.ai:documentation/static/oauth/client-metadata.json(MCP OAuth client)documentation/static/oauth/huggingface-client-metadata.json(Hugging Face provider client)Why
logo_uriis standard OAuth client metadata (RFC 7591 §2). Authorization servers that resolve the CIMD can show the goose logo on their consent screen instead of a generic placeholder, so users see who they're granting access to.Details
https://goose-docs.ai/img/logo_light.png— the square (3370×3370) black goose mark already served by the docs site. The black-on-transparent variant renders on the light backgrounds consent screens typically use (logo_dark.pngis white and would be invisible).