November 6, 2026

Slack will follow your Omarchy theme live

0

A community contribution plugs Slack Desktop into Omarchy’s theme switcher, passing your theme’s key colors and light or dark mode straight into Slack’s own custom-theme settings.

GitHub card for omacom/omarchy pull request #17113, 'Sync Slack's native theme with Omarchy', by acrogenesis on October 30, 2026: 15 files, 13 commits, +561 -2

Image: omacom/omarchy pull request #17113 (GitHub)

Switch your Omarchy theme and Slack switches with it. Pull request #17113, “Sync Slack’s native theme with Omarchy”, opened by community contributor @acrogenesis and just merged by Ryan Hughes into the quattro branch, makes Slack Desktop follow Omarchy theme changes live. It is coming in a future version of Omarchy.

The approach is deliberately light-touch. According to the PR, Omarchy passes the theme’s background, accent, green and red colors into Slack’s native custom-theme fields, along with light or dark mode, and Slack derives its own shades and text contrast from there. Slack’s standard light and dark surfaces keep their native styling: “this does not replace the full Slack palette with Omarchy CSS.”

Under the hood, the theme is rendered from a new slack.json template alongside Omarchy’s other themed apps, and published with the same batch that retints everything else when you change themes. A small Python helper launches Slack, watches the theme files for changes and applies them to open windows, including after reloads, then exits when Slack does. The packaged desktop entry keeps its flags and URL handler.

Setup and removal go through Omarchy’s existing commands. On an existing installation, the PR says to run omarchy setup slack and then fully reopen Slack once to activate it.

The PR reports that live Slack was exercised across ten themes, with reload persistence verified and light-theme headers checked for readability, and that no writes to Slack’s account preference API were observed.

There is one caveat, spelled out in the PR itself: the bridge “uses internal Slack client actions rather than a public automation API, so Slack client changes may require an adapter update.” In other words, a future Slack release could break the sync until Omarchy catches up.

Source: https://github.com/omacom/omarchy/pull/17113

Leave a Reply

Your email address will not be published. Required fields are marked *