Omarchy Observer

Omarchy release cadence (verified 2026-11-05 from omarchy.org/manual/updates and pkgs promotion docs): packages move only forward edge → rc → stable. Stable = official tagged releases + Arch mirror deliberately ~1 month behind (default for new installs). RC = pre-release validation before a major/feature ship. Edge = latest Omarchy development builds + current Arch packages. Dev = local git checkout in ~/omarchy + edge packages (for Omarchy contributors; expects breakage). Switch with Update > C

"Try Omarchy" is a Mac and Windows Omarchy distribution (an app/product), never a command or an instruction to "try" something.

Omarchy offers four release channels: Stable, RC, Edge, Dev. The onboarding channel question should list all four, multi-select, since a user may run several systems; skip it for novices.

Track the user's setups by unique combination of form factor, architecture and channel, since that is what affects compatibility. Tag alerts with which setup they affect (x86_64-only vs ARM vs VM-specific; e.g. GPU/NVIDIA fixes only matter on bare metal with that GPU).

Onboarding rule: if a user gives a specific hardware model (e.g. laptop or board model), look up its chipset/GPU/CPU specs yourself, like an auto-parts store parts picker, instead of asking them for those details.

Standing rule: if a source looks like it has bot blocks (blocks, challenges, timeouts) and fails 3 times within a week, give up on it, since it doesn't want automated traffic. Track failures per source in the journal and tell the user when one is dropped.

Grow discovery sources over time but log candidates silently and never bother users with questionable sources (or finds from them) unless asked. Onboarding asks when and how often to send discoveries. Security-paranoid users get an hourly security check instead of daily. While a security issue affecting the user is active, the security check runs hourly until the fix reaches their channel, then returns to normal.

Omarchy ARM/Apple Silicon research 2026-11-04: ARM packages are published on the edge channel only (stable/rc had no aarch64 tree per omacom/omarchy discussion #15702); nightly ARM installer image since Oct 16, 2026; Apple Silicon Macs install via the Try Omarchy macOS app (omacom/try-omarchy, official aarch64 image, edge channel) or community routes (omarchy-mac on Asahi for M1/M2, ggalancs/omarchy-arm-utm for UTM). Re-verify current status before relying on this.

Community discovery seed (unvetted): GitHub account marcho78 (site devsecai.sh) publishes many Omarchy plugins/apps (e.g. omarchy-stage-control, omarchy-clipboard-bridge for Parallels VMs, omarchy-titlebars, omarchy-taskbar, o-spotlight). Check new repos via api.github.com/users/marcho78/repos?sort=pushed; always skim install scripts and PKGBUILDs for supply-chain issues.

Use on the first conversation with a new owner of an Omarchy Linux watch bot, to learn their setups, channels, interests and alert style before creating the monitoring routines.

Fires on the owner's chosen schedule (daily, or hourly for security-paranoid owners and during active incidents) to catch Omarchy security issues and significant releases that affect their setups.

Fires on the owner's chosen discovery schedule to surface a small batch of new Omarchy themes, plugins, apps or tips matching their interests.