Skip to content

feat(seer): Add optional runId guard to analyze_issue_with_seer - #1270

Open
sergical wants to merge 1 commit into
mainfrom
feat/seer-run-id
Open

sergical wants to merge 1 commit into
mainfrom
feat/seer-run-id

Conversation

@sergical

@sergical sergical commented Aug 27, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds an optional runId input to analyze_issue_with_seer.
  • Sentry's GET /issues/{id}/autofix/ only exposes an issue's current run (validated in ~/src/sentry group_ai_autofix.py), so runId acts as a guard rather than a fetch: when set, the tool never starts a new run, and returns a mismatch message if the issue's current run differs.
  • Motivation: webhook consumers (seer.* Integration Platform events) already hold run_id and should not receive a different run's results or trigger a new run by accident.

Test plan

  • vitest run src/tools/catalog/analyze-issue-with-seer.test.ts — 11 passed (two new cases: mismatch, match)
  • tsc --noEmit for @sentry/mcp-core — 0 errors
  • biome check on changed files
  • generate-definitions re-run; toolDefinitions.json / skillDefinitions.json updated

Created with Claude Code

Webhook consumers already hold a Seer run id. Sentry's autofix endpoint
only exposes an issue's current run, so when runId is given the tool
refuses to start a new run and returns a mismatch message instead of a
different run's results.

Co-authored-by: Claude <claude@anthropic.com>
@sergical
sergical marked this pull request as ready for review August 27, 2026 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant