feat(seer): Carry structuredContent on the ToolResult client model#120569
Open
azulus wants to merge 1 commit into
Open
feat(seer): Carry structuredContent on the ToolResult client model#120569azulus wants to merge 1 commit into
azulus wants to merge 1 commit into
Conversation
azulus
marked this pull request as ready for review
July 24, 2026 22:39
seer emits frontend-only effects (e.g. navigation deep-links) on a tool result's structuredContent, but the client model dropped it (extra=ignore), so it never reached the Explorer frontend. Add an additive optional structuredContent pass-through so the chat endpoint's .dict() serialization carries it to the client; absent on old seer responses, ignored by old clients. Co-Authored-By: Claude <noreply@anthropic.com>
azulus
force-pushed
the
jeremy/effects-registry-wire
branch
from
July 24, 2026 22:43
5c31cf6 to
e96a306
Compare
gricha
approved these changes
Jul 24, 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
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.
seer emits frontend-only effects (deep-links) on a tool result's structuredContent, but the ToolResult client model dropped it (extra=ignore), so it never reached the Explorer frontend. Add an additive optional structuredContent pass-through so the chat endpoint's .dict() serialization carries it to the client.
Absent on old seer responses and ignored by old clients — no behavior change on its own and no required deploy order.
Backend half of the links bus (getsentry/seer#7507); the frontend render lands separately in #120570 and depends on this.