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
UI-only conditional rendering and minor layout tweaks; no auth/data-path changes and behavior is constrained to the settings header.

Overview
Limits the Settings header’s “Restore defaults” action to only render on /settings/general (using useLocation), avoiding misleading/non-functional UI on other settings routes.

Extracts the button into a small RestoreDefaultsButton helper wired to useSettingsRestore, and tweaks header sizing classes to keep the header height from visually jumping when the button is absent.

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

Note

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

• Extracts the restore-defaults UI into a new RestoreDefaultsButton component in settings.tsx
• Uses useLocation to check if the current path is /settings/general, and only renders RestoreDefaultsButton when it matches
• Behavioral Change: the 'Restore defaults' button no longer appears on other settings routes (e.g. account, appearance)

^{Macroscope summarized 625fce1.}

[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: c9021ff5-127c-4e78-88c0-4757ba74c711

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 UI fix that conditionally hides the 'Restore defaults' button on non-General settings pages. The change extracts a component and adds a pathname check - straightforward, self-contained, and low risk.

^{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.}

Dismissing prior approval to re-evaluate b8eceea