feat(seer): Add LLM context to widget builder page#112703
Open
Mihir-Mavalankar wants to merge 1 commit intomasterfrom
Open
feat(seer): Add LLM context to widget builder page#112703Mihir-Mavalankar wants to merge 1 commit intomasterfrom
Mihir-Mavalankar wants to merge 1 commit intomasterfrom
Conversation
github-actions
bot
added
the
Scope: Frontend
Mihir-Mavalankar
force-pushed
the
mihir-mavalankar/feat/widget-builder-llm-context
branch
from
0937545 to
ec1ddd1
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
gggritso
reviewed
Apr 10, 2026
Member
gggritso
left a comment
gggritso
left a comment
There was a problem hiding this comment.
Makes sense overall but the "dummy" context is very strange. This would be tidier if you set the LLM context in the UI component that renders the widget builder, which will make test setup easier, too, since that code already exists
Comment on lines
+69
to
+83
| useLLMContext({ | ||
| contextHint: | ||
| 'Sentry widget builder. The user is configuring a dashboard widget. visualize is the y-axis metrics (timeseries) or the aggregate (big number/table). fields are group-by columns (timeseries) or visible columns (table). query filters the data and sort controls ordering.', | ||
| mode: isEditing ? 'editing' : 'creating', | ||
| title: state.title, | ||
| description: state.description, | ||
| dataset: state.dataset, | ||
| displayType: state.displayType, | ||
| visualize: state.yAxis?.map(generateFieldAsString), | ||
| fields: state.fields?.map(generateFieldAsString), | ||
| query: state.query?.map(readableConditions), | ||
| sort: state.sort?.map(s => (s.kind === 'desc' ? `-${s.field}` : s.field)), | ||
| thresholds: state.thresholds, | ||
| legendAlias: state.legendAlias, | ||
| }); |
Member
There was a problem hiding this comment.
Could you move this out of the custom context and put it directly into the UI component that renders the builder? It's a very unusual pattern to have a loose <WidgetBuilderLLMContext /> component. The name implies that it's a context provider, which it is not, and the fact that is has no children makes it even more confusing. All the state you need is available via hooks.
Contributor
Author
There was a problem hiding this comment.
Re-worked it, lmk if that looks good.
Register a 'widget-builder' node in the LLM context tree so the Seer Explorer agent understands what widget the user is configuring. Pushes builder state (dataset, displayType, visualize, fields, query, sort, thresholds, legendAlias) with readable condition transforms. Also adds the widget builder routes to STRUCTURED_CONTEXT_ROUTES so structured context is sent instead of ASCII when the builder is open. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Mihir-Mavalankar
force-pushed
the
mihir-mavalankar/feat/widget-builder-llm-context
branch
from
ec1ddd1 to
423f37a
Compare
gggritso
approved these changes
Apr 10, 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
2 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.
Register a 'widget-builder' node in the LLM context tree so the Seer Explorer agent understands what widget the user is configuring. Pushes builder state (dataset, displayType, visualize, fields, query, sort, thresholds, legendAlias) with readable condition transforms.
Also adds the widget builder routes to STRUCTURED_CONTEXT_ROUTES so structured context is sent instead of ASCII when the builder is open.