Skip to content

feat(seer): Grant seer:write to Seer agent tokens by default - #127503

Draft
sebastianv1 wants to merge 1 commit into
sebastianshanus/aiml-3633-seer-write-autofix-analysisfrom
sebastianshanus/aiml-3633-fix-autofix-write-scope-errors-in-ask-seer
Draft

sebastianv1 wants to merge 1 commit into
sebastianshanus/aiml-3633-seer-write-autofix-analysisfrom
sebastianshanus/aiml-3633-fix-autofix-write-scope-errors-in-ask-seer

Conversation

@sebastianv1

Copy link
Copy Markdown
Contributor

Summary

Changes

Test plan

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 15, 2026
@linear-code

linear-code Bot commented Oct 15, 2026

Copy link
Copy Markdown

AIML-3633

@sebastianv1
sebastianv1 force-pushed the sebastianshanus/aiml-3633-fix-autofix-write-scope-errors-in-ask-seer branch from 819c8db to e874534 Compare October 15, 2026 14:05
@sentry

sentry Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Sentry Snapshot Testing

Name Added Removed Changed Renamed Unchanged Skipped Status
sentry-frontend
sentry-frontend
0 0 0 0 630 0 ✅ Unchanged

⚙️ sentry-frontend Snapshot Settings

@sebastianv1
sebastianv1 added this pull request to stack #127556 October 15, 2026 15:17
@sebastianv1
sebastianv1 force-pushed the sebastianshanus/aiml-3633-fix-autofix-write-scope-errors-in-ask-seer branch 2 times, most recently from 9aefd4a to fbd3c29 Compare October 16, 2026 16:10
Agent tokens carry `seer:write` without an approval, still capped by the
user's own role scopes. The Seer agent can then re-run Autofix root
cause, solution, and code changes when a user steers them from Seer
chat, instead of stopping on a write-permission prompt for
`event:write`.

Opening a pull request or handing off to a coding agent still needs
`event:write`, so those steps keep the approval prompt.

The rule for adding to `AGENT_DEFAULT_WRITE_SCOPES` is written beside it:
the action must stay inside Sentry and change only Seer's own output.

Fixes AIML-3633
@sebastianv1
sebastianv1 force-pushed the sebastianshanus/aiml-3633-fix-autofix-write-scope-errors-in-ask-seer branch from fbd3c29 to f8d2697 Compare October 16, 2026 17:26
@github-actions

Copy link
Copy Markdown
Contributor

Backend Test Failures

Failures on 57211eb in this run:

tests/sentry/hybridcloud/tasks/test_backfill_outboxes.py::test_watermark_report_skips_a_table_the_loop_never_reached[MONOLITH] — log
[gw1] linux -- Python 3.13.15 /home/runner/work/sentry/sentry/.venv/bin/python3
tests/sentry/hybridcloud/tasks/test_backfill_outboxes.py:382: in test_watermark_report_skips_a_table_the_loop_never_reached
    assert AuthProvider._meta.db_table not in reported
E   AssertionError: assert 'sentry_authprovider' not in {'auth_authenticator', 'auth_user', 'sentry_apikey', 'sentry_apitoken', 'sentry_authidentity', 'sentry_authprovider', ...}
E    +  where 'sentry_authprovider' = <Options for AuthProvider>.db_table
E    +    where <Options for AuthProvider> = AuthProvider._meta

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant