feat: add React component labels for agents#305
Merged
Conversation
Expose session-local component labels in React agent summaries and allow label-based node lookup.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Accept stable component labels in the CLI React runtime store. Keep numeric nodeId support and cover the live command path.
Document label-based React node lookup support.
Bring PR 305 up to date with the latest main branch.
Reinstate label maps and state-aware summaries after merging main.
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 session-local component labels to React agent node summaries. React tools continue to support numeric node IDs, but agents can now use compact labels such as
@c2when reading nodes, children, props, state, and hooks.How does it work?
The React tree store rebuilds a deterministic label map whenever the tree syncs. Node summaries include
labeland, when available,parentLabel. Existing lookup tools accept either the originalnodeIdfield or a newidfield that can contain a numeric ID or label, and the domain schemas describe both forms. Search scoping also accepts labels forrootId.Why is this useful?
Labels make React inspection easier to drive from agent workflows because callers can refer to components with short stable names within the current tree snapshot. Existing numeric ID usage remains valid, while label-based lookup reduces copying mistakes and makes follow-up inspection calls easier to read.