---
title: Settings Home (landing page, changed-from-default, reset)
---

# Settings Home

## What it is

**Settings Home** is the landing page you see when you open Settings fresh — a one-screen overview that answers "where do I find it?" and "what have I changed?" before you ever scroll a section list. It is the first row of the Settings sidebar (a pinned **Home** entry above the six section groups) and contains, top to bottom:

- **Find any setting** — a large search box, the same settings search that normally lives in the sidebar, placed front-and-center. Type a setting's name ("theme", "submit key"), a synonym ("dark mode"), or a category ("performance"); pick a result and Settings jumps to that section and scrolls to the exact control, briefly highlighting it.
- **Popular settings** — about eight tiles for the settings people reach for most (Theme, Font Size, Sidebar Position, Low Power Mode, the global hotkeys, data retention, data folder). A tile is a shortcut, not a copy of the control: clicking it jumps to the real row on its real page, so what you see there is always the live truth.
- **Recently changed** — the last settings you personally changed (newest first), so you can get back to yesterday's tweak without re-hunting it. Click a row to jump to that setting. This list lives only on this computer, remembers roughly the last 20 distinct settings, and only records deliberate changes you make inside Settings — background bookkeeping (a pane you resized, a sidebar you collapsed) never appears in it.
- **Changed from default (N)** — every setting whose value differs from what Omniscio ships with, each row showing the current value, a jump to the row, and a one-click **Reset**. Reset writes the shipped default through the normal save path (you'll see the usual "Settings saved" confirmation, and the row leaves the list). This is the fastest "why is it acting weird?" recovery tool: skim the list, spot the surprise, reset it.
- **Browse all settings** — one card per sidebar group (General, Accounts & AI, Sessions & Workflow, Connections, Built-in Apps, Access & Sharing, Tools & Maintenance) with a clickable chip for every section inside it — a whole-map view of Settings on one screen.
- **Quick links** — one-tap shortcuts to Backup & Restore, Setup Wizards, and Keyboard Shortcuts.

Two related touches ship with Home:

- **A "changed" dot on setting rows.** Across the standard settings pages, any control whose value differs from the default shows a small accent dot next to its label; hovering the row reveals a tiny Reset button right there (on phones the Reset shows without hover). The dot's tooltip says "Changed from default"; the Reset button's tooltip previews the default it will restore.
- **"On this page" chips on long pages.** The Sessions page (about 50 settings) now has grouped subsections (Basics, Composer & input, Mobile, Capacity & engine, Waiting, Spending limits, Behavior, Visibility, Recipes, Extras) with a sticky chip row at the top — click a chip to jump to that cluster.

## Where to find it

Open Settings — the gear icon in the toolbar, the **Settings** entry in the Omniscio sidebar group, or the mobile tools menu. A fresh open lands on **Home**; reopening later in the same app session returns to the section you last visited. On a phone there is no Home row, because the mobile Settings menu is the overview instead.

## How it behaves

### How to use it

1. **Open Settings** (gear icon, the Omniscio sidebar entry, or the mobile tools menu — see [open-settings.md](open-settings.md)). A fresh open lands on Home. Reopening later in the same app session returns to the section you last visited instead — Home is the default, not a hijack. Deep links (an error toast's settings button, right-click → setting, a search hit) always go straight to their target.
2. **Search first.** The big search box is focused and ready on a normal desktop open — just start typing. Results appear beneath it and the rest of Home (popular tiles, your lists, browse cards) collapses while you type, so the matches are the whole page instead of a band above the browse content; clear the box to bring the overview back. **ArrowUp/Down** move the highlight, **Enter** opens it.
3. **Undo a mystery.** If Omniscio behaves oddly, open Home and skim **Changed from default** — a setting you (or an approved automation) changed weeks ago is usually the culprit. Click **Reset** to restore the shipped default, or click the row to inspect it in place first.
4. **Get back to yesterday's tweak.** **Recently changed** lists your latest changes — click one to jump straight back to it.
5. **On a phone** there is no Home row — the mobile Settings menu already is the overview. Instead, the menu screen shows compact **Recently changed** chips and a short **Changed from default** list (with the same Reset buttons) above the section groups, appearing only once you've actually changed something.

Home never contains editable controls of its own, so there is nothing on it to "set" — it is a launchpad. Everything it shows updates live from the same settings store the real pages use.

## For agents

### How it works

The Home page is a normal settings section (`home`) rendered by [SettingsHome.tsx](../../src/renderer/src/features/settings/sections/home/SettingsHome.tsx); its pinned nav row is a label-less first group in [Settings-section-groups.tsx](../../src/renderer/src/features/settings/Settings-section-groups.tsx) (desktop-only — the mobile menu screen serves as home). The landing rule in [Settings.tsx](../../src/renderer/src/features/settings/Settings.tsx) is a precedence chain: an explicit deep-link section wins, then the section you last visited this app session, then `home`.

"Changed from default" derives from a pure comparison of your current settings against Omniscio's shipped defaults ([changed-from-default.ts](../../src/renderer/src/features/settings/changed-from-default.ts)). The list of comparable settings is itself derived — exactly the settings with a real control in the UI — so internal bookkeeping flags can never appear, and secret-bearing keys (API keys, passphrases) are excluded entirely: they are never diffed, listed, or reset. Reset calls the same `updateSetting` path a manual change uses, inheriting persistence, rollback on failure, and the saved-confirmation toast. The per-row dot is the same check run by each row component ([ChangedFromDefaultBadge.tsx](../../src/renderer/src/features/settings/registry/rows/ChangedFromDefaultBadge.tsx)).

"Recently changed" is stored only on this device (browser localStorage, capped at 20 entries, one per setting). Recording happens inside the settings store's save path under the same gate as the "Settings saved" toast — a successful, value-changing save made in the Settings view — so incidental UI-state persists never pollute it. Labels are resolved at display time from the live settings index, so a renamed setting shows its current name (and a removed one falls back to a readable key with no jump). The behavior contract with test locks is [settings-home-contract.md](../../.claude/memory/contracts/settings-home-contract.md).

## Related

- [open-settings.md](open-settings.md) — the three ways in, four ways out, and the landing rules
- [text-size.md](text-size.md) — one of the popular tiles (Font Size) explained
- [settings-search-telemetry.md](settings-search-telemetry.md) — the local-only log behind search-ranking improvements