feat: add React getComponent agent tool#306
Merged
Merged
Conversation
Add combined React component inspection for selected props, state, and hooks.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Document the new React agent component snapshot lookup.
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
1 participant
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 is this?
This PR adds a
getComponenttool to the built-in React agent domain. The tool gives agents one call for a component summary plus inspected props, state, and hooks, instead of requiring separate calls for each section.How does it work?
The React tree store reuses the existing full inspection request path and returns the requested sections from the inspected snapshot. Callers can choose which sections to include and can bound nested serialization depth. The response includes node details, selected inspection data, and partial-result metadata when React DevTools does not provide every requested section.
Why is this useful?
Agents can inspect a component faster and with less orchestration. The existing paginated props, state, and hooks tools remain available for larger data, while
getComponentcovers the common case where a compact component-level snapshot is enough to decide the next debugging step.