Omarchy 4.5 RC Tips: Per-Monitor Workspaces, Floating Desktops and New Apps

As checked on 2026-10-26, v4.0.6 is the latest stable release and v4.5.0-rc1 is a prerelease. This guide keeps eight groups of RC workflows separate from stable instructions. Features and parameters were checked against the v4.5.0-rc1 tagged manual, without physical Omarchy testing here.

Sources: v4.0.6, v4.5.0-rc1. Release timestamps use UTC when precision matters: v4.0.6 was published October 19 UTC, October 20 in Beijing.

1. Give each monitor its own workspaces 1–10

RC change: Super + 2 selects workspace 2 on the focused monitor while the other display keeps its workspace. Workspace 1 can hold code on the main screen and reference material on the second.

Test with disposable windows on both displays. Compare moving a single window with moving its workspace. Disconnect the second display: its workspaces should join another display after existing workspace numbers. Reconnect it and check their return to the original monitor and numbering before migrating custom workspace rules.

Source: RC Navigation.

2. Try floating workspaces with a dock

In RC, Super + L cycles dwindle → scrolling → floating; Super + Alt + L cycles backward. Layout is remembered per workspace. This differs from floating one window with Super + T.

Floating workspaces add themed titlebars and a dock. Minimize with Super + M, then restore through the dock. Double-click a titlebar to maximize while retaining the top bar. Middle-click a dock app for a new window; right-click to pin it.

omarchy dock position left
omarchy dock autohide on

Test overlap, minimize/restore, and fullscreen behavior before moving daily work. Choose the default under Trigger → Appearance → Workspace Layout. Populated workspaces can retain their current layout, so one empty workspace changing does not prove all workspaces changed. Cycle back to restore a workspace, and return dock settings to their recorded values.

Source: RC floating workspaces.

3. Snooze notifications by source and inspect code exceptions

RC notifications stack by app or website. Hover to expand, right-click to snooze a source, and right-click the bar bell to open the panel for history, held notifications, and preferences. Screen sharing offers timed snoozing; the offer does not mute anything until selected.

Before presenting, test an ordinary notification and a verification-code notification separately. Codes can pass through quiet mode by default. Inspect that preference if codes must stay off a shared screen.

Merge preferences into the existing notifications object in shell.json, for example:

"notifications": {
  "fontScale": 120,
  "historyHours": 0
}

This is a fragment. historyHours: 0 disables notification history on disk, rather than clearing every application's logs. Record previous values for undo. Copy code excludes the code from ordinary clipboard history and clears it after a minute; this does not cover unrelated manual copies or source-app records.

Source: RC Notices.

4. Use Appearance and distinguish language from input

Trigger → Appearance groups bar, animation, workspace, and window settings. Try menu controls before writing overrides. RC also remembers a wallpaper per theme and adds a no-animation mode. Release performance descriptions are upstream claims, not measurements reproduced here.

Setup → Language switches the interface language live. Interface language, XKB layout, and Fcitx5 input engines remain separate settings. A Chinese interface does not prove a Chinese engine is installed. Test input in a browser, terminal, and editor, plus the layout used for the lock-screen password.

The RC installer adds Chinese, Japanese, and Korean input choices. Stable users can keep following the Fcitx5 and Rime guide.

Sources: RC release, RC appearance and toggles.

5. Present Markdown with Hype and fill PDFs with Signed

Launch Hype from the app launcher. A deck is one Markdown file with neighboring images and videos. Edit, reorder slides, present fullscreen, or export PDF and PowerPoint. Start with a three-slide sample and check fonts, non-Latin text, media, and exported files before a real presentation. Press ? for shortcuts.

Signed replaces Xournal++ for the default signing workflow in RC. Work from a PDF copy, place text, a date, and a saved signature, then save and inspect every page in another viewer. Placing a signature on a page does not establish a certificate-based digital signature or a particular legal certification.

The stable Xournal++ instructions remain in Web Apps and PDFs. A changed RC default is not a reason to remove a tool you still use.

Source: RC GUIs / Hype / Signed.

6. Record a camera with Monologue and inspect storage with Disktree

Monologue records the webcam rather than the desktop. Choose camera and microphone, check the input meter, and press Space to start, pause, and resume one take. Stop, split and trim in its editor, then save an MP4. Record ten seconds first and check picture, sound, and background privacy. Originals remain until discarded; export is not deletion.

Use Disktree to inspect the home-directory treemap when space runs low; disktree --disk expands the scan to the disk. Inspect before selecting anything for deletion. Large blocks can be project dependencies, models, or virtual disks. Distinguish replaceable downloads from unique work before removing files.

Source: RC GUIs / Monologue / Disktree.

7. Switch agent subscriptions for new sessions

The RC Agents Panel can add and switch multiple subscriptions for a provider. Start with its + button, use clear Personal/Work names, and verify the identity in each authorization browser window.

After switching, open a new session and check the account. Existing sessions keep the account they started with. Account selection also does not fully isolate conversations, project configuration, skills, or plugins. Keep work and personal directory and permission boundaries explicit.

Keep usage notifications first and observe their behavior before enabling Autoswitch. Supplier limits, account policies, and bills remain authoritative. This guide does not copy credentials or recommend moving authentication directories manually.

Source: RC AI / Several subscriptions.

8. Test screenshot and dropdown-console bindings after migration

RC replaces Tensaku with Omasnap for the default screenshot workflow and adds Super + Shift + S. Record existing third-party capture bindings first so two tools do not compete for the same key.

The Super + Grave scratchpad appears as a centered dropdown panel with one window and expands when a second app joins. It is useful for a temporary terminal, without creating a process or filesystem sandbox. Move a window back with a binding such as Super + Shift + 1 and verify the exit path.

Check saved images, clipboard, cancellation, default editor, scratchpad visibility, moving windows back, and bindings after a fresh login. Disable duplicate custom bindings before comparing RC defaults.

Sources: RC desktop changes, RC scratchpad.

Continue on stable

You can use the 20 desktop and laptop recipes and latest stable tips without switching channels. For RC reports, record package versions, channel, hardware, reproduction, and redacted logs. A merged PR or a new paragraph in the rolling manual does not establish that your installed package includes the fix.