Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This is a focused settings-page UX fix that keeps existing scope pickers visible and adjusts programmatic scrolling around them. It changes no settings behavior, data contracts, product defaults, or static-analysis configuration. You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Sticky scope sentence and scroll offset apps/web/src/components/settings/SettingsScopeSentence.tsx, apps/web/src/components/settings/settingsLayout.tsx |
The scope sentence gains sticky positioning, a background, and adjusted spacing. Its menu trigger can shrink. The scrollable settings area adds top scroll padding. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Suggested reviewers: juliusmarminge
Merge Risk: 
Minimal · up to 83669
-
No actionable merge-blocking issue is established for the settings scope positioning change. Normal checks and the remaining desktop smoke test can proceed.
Pre-merge checks: 
4
-
Full details: Description check
-
Explanation
The description clearly explains the problem, implementation, scope, verification results, screenshots, limitations, and agent usage. It does not use the template headings, and the scope approval evidence is indirect, but the required information is mostly present.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
|
Taking over this one as maintainer for batch settings-theme-01. I will merge current main into this branch, preserve the focused scope-picker behavior, and refresh tests, review, and verification. Thanks @ashx-j for the fix. No merge is planned in this batch. |
…cope # Conflicts: # apps/web/src/components/settings/SettingsScopeSentence.tsx
|
Note Written by merged current main into the existing branch without rewriting @ashx-j's commits. the final diff is still three styling lines in two files. it keeps the original sticky scope pickers, opaque background, initial spacing, narrow-label shrinking, and scroll padding, while preserving main's current button styling and font size. no actions changed. passed:
waiting on unrelated ci: unverified: electron shell, macos/windows, and native mobile. web and desktop share these settings components; native mobile is unchanged. before, main at scrollTop 520: after, same data and scroll position: |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>



The project and environment scope pickers scroll out of reach on long Settings pages. They now stay pinned above the rows with an opaque background, while the first section keeps its original spacing. Scroll padding leaves room for focused settings; long picker labels can shrink on narrow layouts.
Rebuilt from @ashx-j’s contribution in #20003, preserving the original commits and merging current main. Removed the decorative gradient and explanatory comments; the resulting diff is three changed lines in two files. Web and desktop share this view. Native mobile has separate settings screens; no contracts, providers, or connection paths changed.
Verification on Linux:
settingsScopeAxis.test.ts(6),settingsScopeNavigation.test.ts(16). PR-added tests: 0 → 0; no static-markup tests added for CSS.Recheck after the settings overhaul (#25651): I merged main again with no conflicts. The scope tests and web typecheck pass. On the new Providers page at 1280×800, scrolled to the bottom (463 px), main's picker sits at y=-350 while this branch keeps it pinned at the top of the settings dialog. The project picker menu still opens from that position.
Before, current main, Providers page scrolled to the bottom:
After, same page, data, and scroll position:
Implemented and coordinated with Codex GPT-6.1-Sol in the Codex harness through T3 Code. Tests: Codex GPT-6-Astra; reviews: Claude Opus 5.5 and Codex GPT-6-Sol.
Recheck by Claude Opus 5.5 in Claude Code through T3 Code.