44 features across six areas, prioritized for turning AetherOS into something you actually run every day — grounded in research on Omarchy Linux and adapted to AetherOS's GNOME + always-on Claude-agent architecture, not ported feature-for-feature.
Extend the golden/LKG boot system so Aether takes a filesystem snapshot before any privileged auto-action at active/aggressive autonomy — not only package updates — generalizing the hook so quarantine and cleanup get the same undo guarantee.
the whole pitch of autonomy levels is "reversible auto-actions" — that promise is only as strong as its weakest untested action.
On a failed boot that falls back to LKG, Aether boots into rescue/observe mode, reads the journal/dmesg from the failed attempt, and writes a plain-language incident note waiting in the chat GUI next login — e.g. "kernel panic in nvidia-dkms after last update, rolled back to the 08-24 snapshot."
Omarchy gives you a snapshot to roll back to but no story of why; a static distro can't explain itself. This is the real AI-native leapfrog — self-healing and self-explaining.
A /usr/share/aether/migrations/*.sh mechanism — one-shot, timestamp-named, marker-file-tracked — so future releases can evolve config schemas the agent depends on (autonomy state, action logs, memory store format) without breaking on upgrade.
the agent's own state needs the same forward-compat discipline as the OS around it; skipping this now means painful ad-hoc fixes later.
A hook that intercepts raw apt/dpkg/systemd unit edits done outside the sanctioned update path, warning (not blocking, unless aggressive+locked) that this bypasses snapshotting and the agent's action log.
keeps the "everything reversible" guarantee from silently eroding as power users go around the tooling.
A low-frequency background pass (daily, observe-level, no side effects) checking disk headroom, SMART health, thermal trends, and swap pressure — messaging the user before something breaks: "root partition will fill in ~9 days at current growth rate."
something no static distro can do — Omarchy has no equivalent because it has no agent watching trends over time.
After a kernel, GPU driver, or netdrv-relevant package updates, Aether runs a smoke test — GPU renders, network comes up, audio enumerates, Bluetooth address ≠ NULL — before declaring the update "settled" and pruning the pre-update snapshot.
directly extends the update-manager already shipped — turns "update succeeded" (package installed) into "update actually works" (system still functions).
The Rescue disable path currently kills Aether entirely; add a minimal degraded chat mode — no root privileges, read-only diagnostics — so a user in rescue mode can still ask "what broke?" instead of being dropped to a bare shell.
rescue mode is exactly when a nervous user most wants explanations, and currently that's precisely when the assistant disappears.
ask "make my touchpad less sensitive" resolves to the correct gsettings/dconf key and applies it — a diff preview at active autonomy, applied silently only at aggressive.
the single most obvious way an AI-native OS beats a static one — Omarchy's "Setup menu = edit plain config files" is still manual; Aether can be the settings UI.
A GNOME-extension-backed clipboard manager where Aether can also be asked "what did I copy about the Postgres connection string earlier?" — semantic search over clipboard history, not just a chronological list.
Omarchy's clipboard history is nice; making it searchable by meaning rather than scroll-and-squint is the AI-native upgrade.
After the update-manager runs, Aether posts a human-written summary of what actually changed on this machine — "Firefox went to 142, no config-breaking changes; NVIDIA driver updated, may need a reboot."
raw changelogs are useless to most users; a machine that read the diffs and your hardware profile can tell you what matters.
Register Aether as a GNOME Shell search provider so a question typed straight into the Activities overview routes to Aether and shows an inline answer, or "open chat for more."
removes friction — Super+A is one more shortcut to remember; Activities search is muscle memory GNOME users already have.
Extend GNOME's screenshot tool with a right-click "Ask Aether about this" that OCRs the region and feeds it to chat — for the extremely common "I got an error dialog, what does it mean."
Omarchy has region OCR as a raw text-extraction utility; wiring it straight into troubleshooting is the AI-native version.
A consistent aether toggle <name> CLI + top-bar indicator for night light, DND, game-mode, quarantine-pause, stay-awake — exposed identically via Quick Settings, CLI, and natural language ("turn off notifications for an hour").
Omarchy's toggle consistency — hotkey = menu = CLI, always — is genuinely good UX discipline worth copying structurally, then layering NL on top.
ask "find that PDF about the lease renewal from a few months ago" searches file contents via a local embedding index Aether maintains passively — not filenames, and not cloud.
GNOME Files search is filename/metadata only; a resident agent has a structural advantage a static OS can't replicate without shipping its own daemon.
When Aether's threat-quarantine or cleanup fires, the notification includes one-tap "why," "restore," and "always allow this" — not just a log entry to dig up later.
trust in autonomy features lives or dies on how easy it is to audit and reverse a specific action in the moment.
One AetherOS palette (built on Catppuccin Mocha) drives GTK4/libadwaita, GNOME Shell, the terminal, and a ~/.config/aether/themed/*.tpl mechanism for apps that don't natively theme — switching accent color or light/dark updates everything in one shot.
Omarchy's single best idea, and it's WM-agnostic — GNOME just needs the propagation layer since it lacks Hyprland's single-config-generates-everything model.
ask "make me a theme based on this sunset photo" — Aether extracts a coherent palette, checks contrast ratios for accessibility, and generates the full bundle (Shell, GTK, terminal, syntax highlighting) in one pass.
Omarchy ships a GUI theme builder, but a human still designs it by hand; an LLM-native OS can go straight from vibe to a working, accessible theme.
Ship 15–20 curated Shell/GTK theme variants — Catppuccin flavors plus a few high-contrast/light options — selectable from Settings or aether theme set <name>, switching live with no logout.
matching Omarchy's "22 themes, zero restart" baseline sets a concrete, achievable bar.
Front gnome-initial-setup's form wizard with an optional Aether chat flow — "what's this machine mainly for: work, gaming, a home server?" — steering app selection, autonomy level, and theme, then handing off to standard GNOME screens for anything security-critical.
Omarchy's first-boot is a slick TTY wizard, but still a wizard. Replacing the decision-making parts of setup with conversation, while keeping the security-critical parts as forms, is a real improvement, not a skin.
A "set this up for someone else" path that installs immediately but defers username/password/personalization to the new owner's literal first boot.
directly useful for anyone building machines for family or employees — a real scenario for a genuinely daily-drivable distro.
A Super+K-style overlay that reads current keybindings straight from GNOME Settings/dconf — not a static image — so custom rebinds are always reflected.
Omarchy's cheat-sheet is trustworthy specifically because it's generated from live config, not documentation that drifts.
On top of the cheat-sheet: ask "swap Super+E and Super+F" edits the actual custom-keybinding dconf entries and confirms — no Settings-app spelunking.
the AI-native version of Omarchy's "just edit bindings.conf" philosophy — same power, zero syntax to remember.
Wire the theme engine to also swap a matched Yaru/Papirus icon variant per palette, so file-manager icons don't clash with an otherwise-coordinated desktop.
small detail, but the kind of finish that makes a theme switch feel complete instead of half-done.
ask inline, no context switchA terminal profile with a bound key that pipes the last command and its output straight to Aether chat as context — "why did that fail" without copy-pasting.
the single highest-leverage dev-experience win available to an AI-native OS that Omarchy structurally cannot offer.
Bundle mise as the default polyglot version manager (Node, Python, Ruby, Go, Rust…), wired into a "set up dev environment for this project" flow that reads a repo and installs what it needs.
mise is genuinely best-in-class; Omarchy's adoption of it over asdf/rbenv/nvm sprawl is worth copying outright, and "read the repo for me" is the AI-native add-on.
Ship Docker without adding the user to the docker group by default — documented rationale: that group is effectively passwordless root — with a single guided toggle to opt in.
a genuinely good security default that's cheap to adopt and prevents a whole class of "malicious postinstall script" incidents.
Ship a pre-tuned multiplexer config so a new user gets a usable terminal workspace on day one instead of a blank .tmux.conf.
removes a classic 30-minutes-of-yak-shaving step for anyone coming from a Mac/Windows dev setup.
aether-do for dev tasksExtend the existing aether-do CLI with repo-context awareness — run inside a project, it reads package.json/pyproject.toml/Cargo.toml and answers "how do I run this" without re-explaining the stack every time.
deepens a capability AetherOS already has rather than adding a new surface — cheap, high-value.
Ship both TUIs preconfigured and theme-synced to the active AetherOS palette, launched via consistent keybindings.
small but real — genuinely popular, low-controversy tools that remove setup friction.
Ctrl+R-style history search backed by Aether's memory, so it also matches on intent — "that rsync command with the exclude flags" — not just substring.
fzf-style history search is table stakes; searchable-by-meaning is the differentiator no static distro can match cheaply.
Building on the update-manager and netdrv-partition work already shipped — not re-implementing them.
Before an update batch runs, Aether flags packages historically associated with regressions on this hardware profile and suggests holding those for a validation channel, applying the rest normally.
the updater already handles the mechanics of safe updating; this adds judgment on top — exactly the layer a static package manager can't provide.
A simple two-channel toggle — stable tracks a validated mirror snapshot, testing tracks latest — reusing the updater's existing snapshot/rollback machinery rather than building new plumbing.
gives cautious users a safety margin and power users an opt-in bleeding edge, at low incremental cost since the hard part is already built.
Surface the smoke-test results (§01) directly inside the update-manager's summary, so "update succeeded" and "update verified working" are visibly different states.
closes the loop between two features already shipped and the reliability story — cheap, since both halves already exist.
aether pkg add/drop — natural-language wrapperA thin NL layer over existing package tooling: ask "install a PDF editor" resolves to a concrete package, with a one-line tradeoff note if there are multiple candidates.
removes the single biggest friction point for people coming from an app-store world.
Wire fwupd/LVFS firmware updates into the update-manager UI as a distinct category, instead of leaving it to a separate, easy-to-forget tool.
firmware updates matter for security, battery life, and stability, and are the most commonly neglected update category on Linux.
A single command that resets Aether-owned and package-owned dotfiles to defaults without touching user data — for when local config drift breaks something and snapshot rollback isn't the right tool.
gives support (human or Aether-assisted) a clean "nuke config, keep data" option that complements snapshot rollback rather than duplicating it.
Adopt Omarchy's stance against a bloated notification-center: a DND toggle + lightweight chronological history — but let Aether answer "did I miss anything important while I was in DND?" by summarizing what was held.
keeps the opinionated simplicity Omarchy is right about, while adding the one thing a plain history list can't do.
Formalize the rule — already partly true for autonomy levels and game-mode — that every user-facing mode gets a shortcut, a Quick Settings entry, and a CLI command, then audit existing features against it.
this consistency is Omarchy's most-cited "why does this feel so tight" quality, and it's a design rule, not a feature — cheap to apply broadly.
A dedicated Help/Learn entry offering the live keybinding sheet, a link to the AetherOS manual, and quick-open shortcuts to GNOME/Ubuntu docs — with Aether chat listed first, not an afterthought.
Omarchy treats onboarding docs as first-class rather than an external wiki; AetherOS already has something better to put at the top.
Wrap GNOME's screen recorder with a source-selection prompt (desktop / desktop+mic / desktop+mic+webcam), automatic output naming, and a finished-recording notification with a thumbnail and one-click play.
screen recording is used constantly for bug reports and how-tos; Omarchy's polish here is a good concrete bar.
Bind a screenshot-region-to-text action and a color picker to consistent shortcuts, discoverable from the same capture menu as regular screenshots.
small, frequently-used utilities that are easy to bundle and immediately useful.
A dedicated "What has Aether done" view listing every autonomous action, grouped by day, each with a one-line reason and a revert button — not just log lines in a file.
this is the trust infrastructure underneath autonomy levels; it deserves the same polish as the actions themselves. Omarchy has no equivalent, since it has no agent taking actions.
Explicitly audit AetherOS's power menu — lock/suspend/hibernate/restart/shutdown/logout — end to end, so it doesn't inherit the "no first-class logout" rough edge Omarchy is known to have.
cheap insurance against a known embarrassment in the exact space AetherOS is being compared against.
If a community extension/theme ecosystem grows, adopt Omarchy's model early — decentralized (any git repo installable) but with an official curated directory that runs a basic security-baseline scan before featuring anything, explicitly labeled community, not core.
cheap to set the norm now, before an ecosystem exists organically with no review process at all.