Floating workspaces gain a dock, widgets move into the tray, and Omarchy expands to 50 languages

01Floating workspaces gain a dock and window minimization

dhh proposed and merged omacom/omarchy#15263 into the quattro development branch on October 13. It adds a dock for finding pinned and running apps on floating workspaces, with an app grid, drag ordering and auto-hide. Super + M minimizes a floating window, and the dock restores it. The current PR description also explains how custom web app launchers retain the identity needed to appear in the dock.

Related quattro commits make empty workspaces adopt a changed default layout while preserving occupied workspaces, and prevent an unreadable workspace list from erasing saved layouts: omacom/omarchy@b6af62e285a3 and omacom/omarchy@ed92b0753f95. Another enables titlebars when floating mode starts. The package repository's master branch also received titlebars 0.2.2, adding resizing above a floating window's titlebar, in omacom/omarchy-pkgs@eba2a95f2e9e. These commits are attributed to David Heinemeier Hansson; they do not establish a stable Omarchy release.

02Bar widgets can live inside the tray drawer

dhh proposed and merged omacom/omarchy#15281 into quattro on October 13. The new tray section places widgets after application icons inside the drawer. Widgets can be moved there by dragging or through bar commands, and plugins can select it as their default section. The drawer stays open while a hosted widget's panel is open.

greptile-apps[bot] flagged that cloned trays would hide drawer widgets. The resulting commit records support for tray clones, drop targets when configured widgets are hidden, and protection against putting a tray inside its own drawer: omacom/omarchy@1a161eb5192a. After the merge, jandrusk reported another edge case: moving a widget into the tray section without a tray host could make it disappear, and suggested refusal or fallback placement in omacom/omarchy#15281:issuecomment-6150468044.

03Language selection expands across the desktop and manual

dhh opened omacom/omarchy#15326 on October 13 and merged it into quattro on October 14, outside coverage. Its current description, edited after coverage, describes 50 languages for the menu, desktop shell and Omarchy notifications, plus translated manuals. Language selection updates Omarchy immediately, while third-party applications follow the matching system locale on the next login. English remains the fallback.

The October 13 review by greptile-apps[bot] raised notification corruption from ampersands, overwritten custom menu headings and insufficient checks for translated manual commands. Those were review findings, not proof of defects remaining after merge. The current description says user menu overrides take precedence and manual validation covers links and code blocks. It also identifies limits: terminal diagnostics remain untranslated, right-to-left layouts are not mirrored, and plural-sensitive strings use one form.

04Superwhisper packages reach stable for AArch64

nchudleigh's omacom/omarchy-pkgs#965 added architecture-specific Superwhisper archives while retaining signature and bundled-version checks. ryanrhughes merged it into master on October 13. github-actions[bot] then reported superwhisper-bin 1.0.2-1 published for both x86_64 and aarch64 in edge, rc and stable, in omacom/omarchy-pkgs#965:issuecomment-6137318104.

The PR author reported local package builds for both architectures and earlier 1.0.1 dictation tests in an AArch64 Omarchy VM; these are contributor-reported checks. A separate quattro commit attributed to Ryan Hughes enabled Superwhisper on aarch64 in Omarchy itself: omacom/omarchy@9a10b488b111. Package publication and development-branch integration are distinct steps.

05Theme switches prioritize terminals and previews use less memory

Quattro received several performance commits attributed to David Heinemeier Hansson, with dhh listed among their participants. omacom/omarchy@d8027c90d619 applies terminal colors and the Hyprland reload first, then finishes other application retints in the background for picker and script switches. Serialized batches skip superseded themes, preventing an older switch from applying its colors after a newer one.

omacom/omarchy@8f5ca14e248f replaces routine keyboard-seat polling with input-device watches and recovery handling. omacom/omarchy@4485e28de8a0 bounds clipboard and artwork decoding to display needs, while omacom/omarchy@c9a4af2cdf67 releases image-picker previews a minute after closing. A companion commit adds timing budgets and checks for unexpected idle process starts in omacom/omarchy@f5006bd41a17. These are committed development-branch changes, rather than independently measured performance results.

06Quiet boot shortens the menu wait and adds a direct return path

dhh opened omacom/omarchy#15301 on October 13 and merged it into quattro on October 14, outside coverage. Its current description specifies a one-second quiet Limine default and a System menu action that reboots into the boot menu with automatic boot disabled. Existing explicit timeout settings are preserved during migration.

greptile-apps[bot] requested coverage for denied authentication. dhh reported adding a test that rejects authentication and requires the migration to fail without changing the menu, then adjusted the permission-dependent case to skip under root. The PR still calls for a real reboot to confirm menu reveal and the one-shot boot-menu request; the supplied checks do not independently establish those hardware results.

07Fingerprint retries pause while the lock screen is blank

dhh opened omacom/omarchy#15294 on October 13 and merged it into quattro on October 14, outside coverage. Its current description pauses new fingerprint verification attempts after the lock blanks the displays, allowing an existing attempt to finish. The user-facing trade-off is explicit: wake the screen before using a finger to unlock.

During October 13 review, greptile-apps[bot] found that a repeated idle-lock request could incorrectly restart the reader. dhh reported changing that path to resume only after detecting evidence of suspend. In another exchange, dhh documented that a brightness or volume action unseen by the lock can leave fingerprint checks paused until key or pointer input arrives. greptile-apps[bot] accepted that limitation in omacom/omarchy#15294:discussion_r4259080090.

08Still lock-screen posters remain an open proposal

dhh's omacom/omarchy#15289 opened on October 13 and remains open at the October 19 check. Its current description proposes replacing video-wallpaper playback on the lock screen with the cached blurred still frame, removing the video feed and its periodic display-state queries. This behavior is proposed, not established as merged.

greptile-apps[bot] noted that removing the feed fixture also removed behavioral checks for poster selection and image release. dhh replied that a trimmed offscreen fixture had been restored and mutation-checked. The bot's subsequent October 13 summary said the restored tests addressed its finding in omacom/omarchy#15289:issuecomment-6145843873.

09Memory watchdog proposal separates warnings and pauses from agent intervention

KewkLW opened omacom/omarchy#15272 on October 13; it remains open. Its current body, edited after coverage, proposes an opt-in watchdog that warns before systemd-oomd kills an application, identifies victims afterward and pauses eligible heavy work before the kill threshold. Pausing stops further activity but does not itself free memory. The current scope excludes the agent responder and leaves it for a follow-up.

The October 13 discussion covered a broader implementation. greptile-apps[bot] flagged game protection and pause-record safety, and KewkLW reported revisions including inherited game protection, safer recording and persisted responder handoffs. Those reports describe work under review, not shipped guarantees. jandrusk then recommended landing warnings and pausing separately, calling a headless responder able to kill processes a larger product decision in omacom/omarchy#15272:issuecomment-6150464090. The current narrowed proposal reflects that separation.

10arXiv Assistant is listed after privacy fixes and removal of Codex support

pierrecagne submitted arXiv Assistant through omacom/omarchy-plugin-marketplace#11408 on October 13. It lists preprints from selected categories and generates AI reading reports for starred papers. github-actions[bot] reported publication that evening and closed the submission. Its automated verification applies to the exact marketplace snapshot and is not a security audit.

HANCORE-linux's review prompted successive privacy changes. The reviewer acknowledged that a per-run secret fixed unauthenticated report access, then flagged private reader context exposed through process arguments. pierrecagne reported moving configuration to standard input, making logs and reports private, and tightening permissions on existing recorded reports.

HANCORE-linux also identified that the Codex sandbox exposed its mounted credentials and past sessions to paper-processing tools. pierrecagne acknowledged the finding and removed Codex support instead of shipping an integration they could not test, in omacom/omarchy-plugin-marketplace#11408:issuecomment-6156586127. The remaining engines are Claude Code in its restricted mode and custom commands documented as unsandboxed.

11Build infrastructure moves trusted contributors and ARM kernels to Namespace

emirb proposed and merged omacom/omarchy-iso#269 into quattro on October 13. Install tests now select Namespace runners by author eligibility rather than whether a branch comes from a fork. Collaborators with write access and vouched contributors qualify; failed lookups fall back to GitHub runners.

Copilot flagged that trusting every bot account admitted arbitrary GitHub Apps. A subsequent commit restricts that exception to Dependabot and GitHub Actions. Copilot also explained that a PR-controlled workflow can request a runner directly. The final PR description distinguishes runner selection from security enforcement and identifies repository approval settings as the separate boundary.

In the package repository's master branch, omacom/omarchy-pkgs@3afdffcedf47 moves aarch64 kernel builds to Namespace's Apple-backed runner. The commit, attributed to Emir Beganovic, reports a reduction from 105 minutes on GitHub's ARM runner to 24 minutes there. These are contributor-reported measurements intended to shorten the wait before hardware patches can be tried.

12Super + L remains the workspace-layout shortcut

mattwolfgang's proposal to make Super + L lock the session and move layout cycling to Super + Ctrl + L was closed without merging on October 13. omacom/omarchy#14203 argued that users arriving from Windows or GNOME could mistake layout switching for locking.

dhh declined the swap, citing Omarchy's established use of Super + L for layouts and pointing users who prefer the alternative toward local customization in omacom/omarchy#14203:issuecomment-6156758671. The proposed default shortcut change did not land.