feat(seer): Fix disabled states & tweak design of Seer Projects settings page #106058
Conversation
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
github-actions
bot
added
the
Scope: Frontend
ryan953
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
static/gsApp/views/seerAutomation/components/projectDetails/backgroundAgentFields.tsx
Show resolved
Hide resolved
static/gsApp/views/seerAutomation/components/projectDetails/backgroundAgentPicker.tsx
Show resolved
Hide resolved
…x (2xl) before the Conencted Repos button
ajay-sentry
reviewed
Jan 14, 2026
static/gsApp/views/seerAutomation/components/projectDetails/backgroundAgentFields.tsx
Show resolved
Hide resolved
ajay-sentry
reviewed
Jan 14, 2026
static/gsApp/views/seerAutomation/components/projectDetails/seerAgentSection.tsx
Outdated
Show resolved
Hide resolved
ajay-sentry
reviewed
Jan 14, 2026
| isLoadingIntegrations: boolean; | ||
| preference: ProjectSeerPreferences; | ||
| project: Project; | ||
| selectedIntegration: ReturnType<typeof useCodingAgentIntegrations>['data'] extends |
Contributor
There was a problem hiding this comment.
kind of a funky type, is there a way to tighten it up at all?
ryan953
commented
Jan 14, 2026
static/gsApp/views/seerAutomation/components/projectDetails/seerAgentSection.tsx
Outdated
Show resolved
Hide resolved
ajay-sentry
approved these changes
Jan 14, 2026
Contributor
ajay-sentry
left a comment
ajay-sentry
left a comment
There was a problem hiding this comment.
nothing blocking, couple small things
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.
This is a bigger change in the backend to remove the SeerSettingsFormModal, but otherwise on the UI we're just doing a couple things:
disabledstate to everything, so ~half the fields are disabled when Background Agent is on/offseems like the flow is:
1) we'll handle the initial detection of issues that are "highly actionable" and pull together root cause analysis with telemetry data.
2) you have an option of whether to pass that on to an agent so it can propose some code changes. It could be Seer Agent, or could be a cloud agent.
3) agents will have their own settings, like whether the agent can put those changes into a PR.