Omarchy pulls Slack theme sync before it ships after Slack 4.53 refuses to launch with it
Slack 4.53 now rejects the debugging flag Omarchy’s live Slack theming depended on, so DHH has reverted the feature and added a migration to hand Slack back its own launcher.
Image: omacom/omarchy pull request #18788 (GitHub)
The live Slack theming we covered earlier this month is gone before it ever reached a release. DHH merged pull request #18788, “Remove Slack theme sync”, into the quattro branch on November 14, 2026. It reverts #17113, the community contribution that made Slack follow your Omarchy theme live.
The reason is a change on Slack’s side. According to the PR, Slack 4.53 refuses any --remote-debugging-* switch on its default profile, and Omarchy’s theme sync worked by starting Slack with --remote-debugging-pipe. The result: Slack prints “Refusing to launch: –remote-debugging-pipe requires –user-data-dir pointing outside the default profile” and exits before a window ever opens.
That breaks Slack for anyone running the code with the sync in place. As the PR puts it, “Since Install > Service > Slack turns theme sync on, every fresh Slack install is affected.”
The fix is a clean removal. The theme launcher, its setup and theme commands, the slack.json template and the Slack-specific install and remove commands are all deleted. Install > Service > Slack goes back to the generic omarchy-install-and-launch, and Slack runs from its packaged launcher on its default profile, with its own theme.
For machines that already set up the sync, a migration puts things back. It only touches the slack.desktop override if that file runs omarchy-launch-slack: it restores the original launcher saved as slack.desktop.before-omarchy if there is one, otherwise removes the override, and then deletes ~/.local/state/omarchy/slack. A custom launcher of your own is left alone. Without the migration, the PR notes, those installs “would be left with a launcher pointing at a command that no longer exists.”
DHH did try to keep the feature first. An earlier version of the PR gave themed Slack a separate profile of its own to get around the restriction, but that change was reverted on the branch, so what landed is the removal only.
The PR says the migration was run against scratch homes and that, on a Snapdragon laptop with slack-desktop 4.53.287-1, Slack opens from the app launcher once the override and state are removed. The full Install > Service > Slack flow was not checked end to end, since Slack was already installed on the test machine.
If you are on Omarchy 4.5.0, nothing changes for you: the Slack theme sync files are not in the v4.5.0 tag, the latest release. The removal and its cleanup migration are coming in the next version, and the live Slack theming is not coming with it.
