fix: show restore defaults only on General settings

[UtkarshUsername]

Fixes #1709

What Changed

Moved the Restore defaults visibility check into the shared settings header so the button keeps its existing placement but only renders on /settings/general.

Also kept the web settings header height stable between General and Archive so the header does not visually jump when the button is absent.

Why

Restore defaults resets general settings values. Showing it on the Archive page is misleading because that page is not a settings form and the action does not belong to that section. Also, the button doesn't work on the Archive page.

Keeping the button in the shared header preserves the original UI placement, while route-gating it makes the behavior correct. Fixing the header height avoids a visual regression between settings routes.

UI Changes

Before:

After:

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Low risk UI change that only gates rendering of an existing button by route and adjusts header sizing; no data/model changes.

Overview
Limits the Restore defaults button to render only on /settings/general by checking useLocation().pathname, avoiding showing a misleading action on other settings sub-routes.

Adjusts the non-Electron settings header layout (min-h-*) so the header height remains stable when the button is hidden, while keeping Electron and web headers consistent.

^{Reviewed by Cursor Bugbot for commit e10cab0. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Show 'Restore defaults' button only on the General settings page

The button was previously visible across all settings routes. Now checks location.pathname in SettingsContentLayout and only renders the button when the path is /settings/general, in both Electron and non-Electron headers.

^{Macroscope summarized e10cab0.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 681052f4-d7f8-449b-95a1-85cc103a4f57

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

This is a simple, self-contained UI change that conditionally hides the "Restore defaults" button on non-General settings pages. The logic is straightforward pathname checking with no runtime behavior changes beyond visibility of an existing UI element.

^{You can customize Macroscope's approvability policy. Learn more.}

Dismissing prior approval to re-evaluate f875f19

[cursor]

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 e10cab0. Configure here.}

[cursor]

Hook runs unnecessary computation on non-general settings pages

Low Severity

useSettingsRestore is called unconditionally on every settings route (general, archived, connections), but its return values (changedSettingLabels, restoreDefaults) are only consumed when showRestoreDefaults is true (i.e., on /settings/general). The hook internally subscribes to useTheme(), useSettings(), and useUpdateSettings(), computes dirty state across multiple settings, and builds memoized arrays and callbacks—all wasted work on the archived and connections pages. Moving the hook call behind the showRestoreDefaults condition (or into a child component rendered only on general) would avoid this unnecessary computation and context subscriptions.

 

^{Reviewed by Cursor Bugbot for commit e10cab0. Configure here.}