CJK input reaches menu search, font preferences and installer choices
dhh merged
omarchybot's omacom/omarchy#15508 into the quattro development branch on October 15. The corresponding commit enables input-method composition in menu search, adds controls for Japanese, Korean and Chinese glyph forms, and themes the Fcitx candidate window. It also preserves an explicit return to default glyph forms so later language setup does not overwrite that choice.
Keyboard changes keep newly configured Hangul, Zhuyin and Cangjie engines on their expected physical positions under alternative Latin layouts. Korean setup accommodates Right Alt and Right Ctrl switching keys, while Hong Kong gains a Cangjie installer choice. The matching ISO validation was committed on quattro as omacom/omarchy-iso@af820ef61395.
In its review response, omarchybot reported testing real Mozc composition in a disposable VM and checking that composed text cannot enter the search field behind an uninstall confirmation. That is contributor-reported validation, separate from the unit tests described in omacom/omarchy#15508:discussion_r4277973486.
Sources
- Support the NVIDIA N1x laptops
- Build one aarch64 image for every board
- Add the NVIDIA N1x kernel, driver and platform packages (#930)
- Build the aarch64 image on the linux-omarchy edge publishes
- ISO build: require signatures on Omarchy's own packages on aarch64 too
- List the ProArt P14's amplifier firmware with the optional packages (#15557)
ARM work joins N1x laptop support with a shared installation image
ryanrhughes merged omacom/omarchy#14820 into quattro on October 15, adding runtime support for NVIDIA N1x laptops. Its current description covers the ASUS ProArt P14 and Dell XPS 16, including platform detection, audio, power management and USB4 docking. The associated kernel, driver and platform package work was committed to the package repository's master branch as omacom/omarchy-pkgs@b6ace05ccc4b; these events do not establish a stable Omarchy release.
birkskyum proposed a shared aarch64 USB installation image in omacom/omarchy-iso#258, which
ryanrhughes merged into the n1x branch. It selects platform packages at installation time and excludes Apple Silicon Macs, whose installation starts from macOS. The proposal documented incomplete hardware validation, including intermittent black-screen boots on a Yoga Slim 7x and no laptop installation test from that image.
Subsequent quattro commits made the image build use the kernel published on edge without requiring a local package bundle, through birkskyum's omacom/omarchy-iso@c65bb6743486.
emirb's omacom/omarchy-iso@c799bfcbdca9 requires signatures for Omarchy packages downloaded into aarch64 images.
ryanrhughes also committed an amplifier-firmware package listing in omacom/omarchy@8a787b6a8bec to prevent an offline ProArt installation from stopping with a missing package.
1Password authorization fix reaches stable packages
dhh merged
calledtoconstruct's omacom/omarchy-pkgs#489 into master after the proposed fix changed during review. Published packages had named the build account as the polkit action owner, affecting CLI and SSH-agent authorization. The original proposal substituted the wheel group, but
omarchybot reported that polkit did not expand that group when checking action ownership.
omarchybot revised the branch to render individual user owners during installation and upgrades, following the vendor's first-ten-users rule for UIDs 1000 through 9999. Its worker report described successful authorization challenges with the corrected package.
github-actions[bot] then reported version 8.12.40-3 published for both architectures across edge, rc and stable in omacom/omarchy-pkgs#489:issuecomment-6193109904. Users created afterward are added at the next 1Password update.
Agent collector proposal tightens credential boundaries and stale usage handling
omacom/omarchy#14040 remained open when checked on October 19. Its current description, updated October 18, proposes a common contract for expanded agent-panel collectors and default-agent launchers. The concrete October 15 activity includes responses under dhh's account, marked as posted by Claude on behalf of DHH, reporting fixes to credential handling and retained usage data.
In omacom/omarchy#14040:discussion_r4279094377, dhh reported restricting proxy redirects and final destinations to the configured scheme, host and port so a key cannot reach another endpoint. Other responses reported separate Antigravity limit caches for each account, retaining Codex's last known windows as stale when a response supplies no limits, and removing obsolete usage files for dropped collectors.
dhh also declined to treat Synthetic's incremental regeneration timestamps as full window resets, explaining that retained answers should remain stale and use only service-provided reset times. The proposal's current description says collector testing used offline fixtures rather than live services or credentials, limiting what those reported checks establish.
Bar rearrangement preserves widgets and changes section layout
outfoxxed opened and merged omacom/omarchy#15517 into quattro on October 15. The change separates the center box from the regions around it and stops recreating widgets during rearrangement.
The PR also describes improved dragging and corrected growth direction for expanding widgets such as the tray and indicators. This is a development-branch merge, with no stable-release event supplied.
China region proposal replaces extra repository trust with Omarchy mirrors
xdanger's omacom/omarchy#13690 remained open at the October 19 check. On October 15,
omarchybot reported pushing five commits and rewriting the description after extending the proposal on maintainer direction. The proposed World or China setting coordinates package mirrors and developer-tool registries for downloads that can be slow or unreachable in mainland China.
The revision removes the additional archlinuxcn repository and keyring, instead prioritizing Omarchy's China replicas of the same signed packages. omarchybot explained that the extra keyring would have widened package-signing trust. The switcher also gained rollback handling and preservation of user registry settings.
omarchybot reported testing a live China-to-World switch, package downloads and developer-tool registries on a fresh worker in omacom/omarchy#13690:issuecomment-6185224082. Those are contributor-reported results; the comment explicitly left the proposal waiting on the maintainer.
Waydroid proposal narrows Android access to host services
EzekielOgunkunle's omacom/omarchy#15503 remained open at the October 19 check. It proposes Android installation and app launching through Waydroid, with individual resizable windows and Install and Remove menu entries. An October 15 comment supplied a screenshot attributed to the contributor's Intel UHD 620 test machine.
Later that day, EzekielOgunkunle reported addressing five review findings in omacom/omarchy#15503:issuecomment-6198075225. The revisions restrict container access to host DHCP and DNS services, give the interactive app picker a terminal, distinguish apps with identical names, and prevent failed package removal from being reported as successful.
The current PR body was updated October 16. As current context, it leaves host file sharing for follow-up work and documents contributor-observed Android compositor crashes under heavier use with the official image on that hardware. The integration remains a proposal.
Ragtop removes typed characters from helper process arguments
In October 13 background discussion on omacom/omarchy-plugin-marketplace#11433, HANCORE-linux identified newly used non-ASCII password characters appearing in helper process arguments. On October 15,
sclemance confirmed a broader typing exposure, said it also affected the listed 0.44.0 snapshot, and reported fixing it in 0.45.1.
sclemance described replacing per-character external lookups with an in-process keymap index and limiting exception reporting so typed text cannot enter journal messages. The contributor reported equivalent lookup results and no character-bearing helper processes during the revised typing test in omacom/omarchy-plugin-marketplace#11433:issuecomment-6198375016.
HANCORE-linux closed the older verification request on October 15.
sclemance requested review of a replacement target, and
github-actions[bot] subsequently committed a Ragtop marketplace update to main as omacom/omarchy-plugin-marketplace@43c2a2b65a0f. The supplied commit message does not identify the version it published.
OMARemote closes automatic clipboard reads and bounds explicit paste
HANCORE-linux challenged the clipboard assumptions behind OMARemote's verification request, pointing out that released Qt code still retrieved clipboard text during automatic paste checks.
RFdeGroot acknowledged checking a newer branch instead of the release and said the earlier focus-based workaround had increased clipboard reads.
RFdeGroot then described keeping fields editable, disconnecting automatic clipboard-change checks, disabling the context menu, and routing explicit paste through a separate process limited to two seconds and 16 KiB. The contributor reported an offscreen test checking that focus and clipboard changes do not retrieve clipboard text in omacom/omarchy-plugin-marketplace#11361:issuecomment-6188195421.
RFdeGroot closed omacom/omarchy-plugin-marketplace#11361 and reported superseding it with a plugin revision requiring OMARemote 0.7.0. This records the reported fix and replacement verification request, rather than a completed marketplace verification.
Third-party store report identifies a persistent update-hook risk
Dankestrick opened omacom/omarchy-plugin-marketplace#11590 to report a third-party store copying marketplace listings and installing a post-update hook. According to the report, that hook downloaded a remote catalog and could install packages with root privileges after an Omarchy update.
Dankestrick explicitly said no malicious payload had been found in the material examined.
In an October 15 follow-up, Dankestrick reported that the domain had been suspended and two associated GitHub accounts removed following abuse reports. The remaining concern was the hook already installed on users' machines: the reporter said it would continue running and could regain its remote installation path if the domain returned. The issue remained open at the October 19 check; these findings and enforcement outcomes are attributed to the reporter.
Theme intro videos move into a separate package
A commit associated with dhh, omacom/omarchy-pkgs@e310103834fc, moved the 20 theme intro videos into a dedicated package on master. The commit explains that the videos accounted for 92 MB of the 160 MB development package and changed rarely, yet were downloaded again with every quattro tip.
Both the development and regular Omarchy packages now depend on the separate video package, pinned to the last commit that changed an intro. This is a committed packaging change; the supplied record does not establish channel publication.
