Repository navigation
Make Grok Build follow the Omarchy terminal palette - #11346
Closed
husamemadH wants to merge 1 commit into
Closed
husamemadH wants to merge 1 commit into
husamemadH wants to merge 1 commit into
Conversation
Grok has no custom theme file, so it stayed on GrokNight while Omarchy retinted the terminal. Point it at theme=terminal (plus the rollout flag) on activate, leave a later /theme choice alone, and migrate existing ~/.grok installs.
Member
|
Automated duplication check: this pull request looks similar to #6521, which covers the same Grok theme sync. I keep that one open and close this one to consolidate review. If you feel this is the wrong decision, please open the PR again with a note on the difference. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Omarchy already retints Claude, Pi, Hermes, T3 Code, and OpenCode. Grok Build is installed the same way, then left on GrokNight, so a theme like Osaka Jade shows a black TUI inside a green terminal.
Grok has no custom theme file to generate. Its
terminaltheme paints no canvas of its own and uses the terminal palette Omarchy already applies to Ghostty/Alacritty/Kitty/Foot.omarchy-theme-set-grok, wired intoomarchy-theme-setandinstall/user/theme.sh--activate(install does this): set[ui] theme = "terminal"and[features] terminal_theme = true--activate: if~/.grokexists and no theme is set (or it is alreadyterminal), write the same; leave a later/themechoice alone~/.grokinstallsRelated: #6521 maps Omarchy slugs onto Grok built-ins (
osaka-jade→oscura-midnight), which still does not match the terminal. #6812 is the right idea but writestheme = "minimal"(Grok's screen mode, not a theme name). This usestheme = "terminal"plus the rollout flag, which is what actually retints Grok onto Osaka Jade.Test plan
./test/cli(no-op without home, activate writes terminal + flag, preserve marketplace tables, leave tokyonight alone,--activatereplaces it, symlink write-through)bash test/shell.d/user-theme-test.sh(finalize always calls--activate)/theme tokyonight, change Omarchy theme → Grok stays on tokyonightomarchy-theme-set-grok --activateresumes follow~/.grok, theme-set without--activateis a no-op