fix: prefer tool title in app view chrome - #749
Open
Chipagosfinest wants to merge 1 commit into
Open
Conversation
Chipagosfinest
marked this pull request as ready for review
August 17, 2026 16:34
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
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 changed
Tool.title, falling back toTool.nameWhy
App views currently expose programmatic identifiers such as
get_report_appeven when a tool already provides a human-readable title. Reusing the standardTool.titlefield fixes the user-facing mismatch without adding redundant app-specific metadata or coupling the display label to the callable tool name.This also matches the broader Mini App pattern where host-provided chrome uses human-readable app/action metadata while machine identifiers remain internal.
Closes #740.
Validation
npm run --workspace examples/basic-host buildnpm run prettiernpm run build:all