ref(autofix): Use local run mirror for automation eligibility - #121026
Open
trevor-e wants to merge 2 commits into
Open
ref(autofix): Use local run mirror for automation eligibility#121026trevor-e wants to merge 2 commits into
trevor-e wants to merge 2 commits into
Conversation
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 277c112. Configure here.
trevor-e
marked this pull request as ready for review
July 31, 2026 23:30
chromy
approved these changes
Aug 1, 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.

Automation eligibility now checks the durable Sentry-side agent-run mirror instead of making a round trip to Seer. Only a live mirror with a Seer state ID suppresses another attempt, so failed or pending dispatches can recover.
Remote state lookups remain in the API state and operator flows that need the full run state.