Omarchy

Bash or zsh on Omarchy? I Kept Bash, Lost 3 Aliases

Omarchy ships bash. I priced out switching to zsh against my own dotfiles: 61 of 64 aliases and my most-used function run in bash. Here is the list.

In this post
  1. Does Omarchy use zsh?
  2. The argument for zsh that fell apart
  3. What bash costs
  4. Why I didn’t force the two machines to match
  5. Do not chsh
  6. If you want zsh anyway
  7. Should you switch?

Omarchy ships with bash, not zsh. You can run zsh on it, and plenty of people do. I decided not to, after checking what bash would actually cost me. The answer was three aliases.

I run Omarchy on an x86 desktop and two MacBooks now. When I wrote this decision down on 2026-09-05, it covered two machines: an Omarchy box and a Mac with ten years of zsh on it. So I had a real reason to want the same shell everywhere. This post is that record, with the how-to parts trimmed down to what you need if you decide the other way.

Does Omarchy use zsh?

No. On my install, the account’s login shell is /bin/bash, and Omarchy’s shell setup lives in /usr/share/omarchy/default/bash/. The rc file in there sources envs, shell, aliases, functions and init, and then loads an inputrc for key bindings.

The init file is where most of what you see in the terminal comes from. It activates mise, starts the starship prompt, starts zoxide, and loads fzf’s key bindings for Ctrl-R, Ctrl-T and Alt-C. A comment in that file says it skips fzf’s bash completion script on purpose, because that script re-wraps about 76 commands’ completions on every shell start and adds around 25ms before the prompt.

Zsh is not part of the default install. It is available as a package, and Omarchy has an omarchy pkg add command for installing one. In the community discussion titled Has anyone tried changing the shell?, a commenter points to separate omarchy-zsh and omarchy-fish repositories, and another says the omarchy-zsh README instructions worked for them. A third commenter in that thread says the official zsh support only sets up functions and aliases, so it does not match what the bash side gives you. I have not tried those repositories, so I can’t say how far apart the two are today.

The argument for zsh that fell apart

My first version of the decision went the other way. I set the terminal to launch zsh on both machines so the interactive shell would be identical. The reason I wrote down was that g, my most-used function in the repo at about 1,100 invocations, is a zsh file, and so is everything in my zsh/configs/ folder.

The part about g was wrong. Here it is:

g() {
  if [[ $# -gt 0 ]]; then git "$@"; else git status; fi
}

It runs git with whatever arguments I give it, or git status if I give it none. [[ ]] is a bash keyword too, so the function body runs unmodified in bash. I hadn’t read that file closely before. Once I did, I reversed the decision the same day, before anything was installed.

Bringing g over did break one thing. Omarchy ships alias g='git', and bash expands aliases in the function-name position when it parses a definition. With that alias live, my g() {...} parsed as git() {...}: a function named git whose body calls git. Every git call recursed about 4,600 levels deep and segfaulted the shell. The fix is one line in my shared shellrc, which runs unalias on each function’s name before sourcing it. If you bring your own functions to Omarchy, check their names against its aliases first.

What bash costs

Once I stopped assuming and went through the repo, the list was short.

What Runs in bash?
g function Yes, unmodified
61 of my 64 aliases Yes
alias -g G, L, M (3 global aliases) No
zsh/configs/* (prompt, completion, keybindings, history) No
zsh/completion/* No

The three aliases I lost are the global aliases G, L and M. Global aliases expand anywhere on a command line, not just in command position, and bash has no equivalent. My decision record listed a fourth, alias -- -="cd -", as zsh-only. While checking this post I ran it in bash 5.3 and it works, so the real count is three.

The bigger loss is the zsh environment: my prompt, my completions, my key bindings and my history options. Omarchy has its own version of each, set up in the init file described above. So the question was whether my zsh setup was enough better than Omarchy’s to be worth maintaining on top of it. I decided it wasn’t. Omarchy updates are written for its bash setup, and if one breaks something in my zsh setup, I’m the one who finds out.

Why I didn’t force the two machines to match

Matching shells on both machines would have bought me one prompt instead of two. That wasn’t worth running zsh against Omarchy’s defaults. The Mac has ten years of zsh habits behind it, so it stays on zsh.

My dotfiles already had the right shape for this. The shared/ folder holds what is shared between machines, and the shell environment was never part of that. The zsh files get linked on Linux and sit there unused.

What I did want on both machines was the tooling, and that turned out to be a question of what is portable between shells. Here is how I split it:

  • shared/shellrc is the portable core, sourced by both shells. It loads the functions from ~/.shell/functions/ (g and mcd), the aliases file, my PATH, and guarded setup for direnv, mise, go, bun and fzf. “Guarded” means each one only runs if the tool is installed.
  • shared/zsh/ holds only what is zsh: change-extension, which uses foreach and glob qualifiers, plus the completions and zsh/configs/*.
  • shared/aliases is one file for both shells. The lines I marked zsh-only are wrapped in if [ -n "$ZSH_VERSION" ], so bash skips them. I had wrapped the - alias too, by mistake, and moved it out while writing this.

~/.bashrc on Omarchy is a real file with machine-local content in it, such as cargo and gcloud setup. My install.sh appends one source line to it and does not symlink over it. That is safe to run twice, and undoing it means deleting two lines. The zshrc on the Mac sources ~/.shellrc first and then adds the zsh-only half.

If you sync dotfiles across machines too, the post on what to sync for Claude Code covers the same repo and the symlink-or-merge decisions behind it.

Do not chsh

If you do go to zsh, the way you do it matters. The discussion Changing Your Shell to Zsh or Fish in Omarchy Without Breaking Everything says that changing the login shell with chsh can leave a black screen after the disk-encryption password, and the author’s explanation is that Omarchy’s boot chain expects bash as the login shell. rpbaptist, in that thread, says they hit the black screen. Another commenter, lbonvarl, says chsh -s /usr/bin/zsh on a non-encrypted manual install gave “no noticable downsides or strange behaviors.” In the other discussion, a commenter named snek says that switching to fish “broke various things because hyprland is started from bash,” and that setting the shell in the Alacritty config avoided it.

Those are reports from other people. I haven’t reproduced any of it, because I never ran chsh on either machine. What I can say is that the advice in both threads matches what I did: leave the login shell alone and tell the terminal which shell to start.

If you want zsh anyway

My dotfiles doc has the reversal written out in case I change my mind. It is short.

Install the package first:

omarchy pkg add zsh

Then set the shell in your terminal’s config. For foot, in ~/.config/foot/foot.ini under [main]:

shell=/usr/bin/zsh

For Ghostty, in ~/.config/ghostty/config:

shell = /usr/bin/zsh

For Alacritty:

[terminal]
shell = "/usr/bin/zsh"

Apply it with omarchy restart terminal.

Edit your files under ~/.config. Do not edit anything in /usr/share/omarchy/, because omarchy update overwrites it.

One order-of-operations rule from the doc: install your zsh configs before you point a terminal at zsh. A terminal that launches an unconfigured zsh is worse than bash. You have no prompt, no completions and none of your functions. In my case that would have meant no g.

Should you switch?

If you have no zsh setup yet, stay on bash. Omarchy’s prompt, completions and key bindings are already wired up, and building a zsh setup from scratch only gets you back to the same place.

If you have years of zsh config, do an inventory like the table above before you decide. Take each alias, function and option and ask whether it runs in bash. I assumed my answer was no for the function I use most, and it was yes. The list of things that really need zsh was three aliases and a folder of shell-environment config, and I could live without all of it on Linux.

If something on your list really needs zsh, the terminal-shell route above is the change to make. Whichever way you go, the Omarchy hub has the rest of what I’ve written about running it day to day, including what broke on the M1 MacBook and why its agent launcher starts coding agents with approvals off.