🙃 A delightful community-driven (with 2,500+ contributors) framework for managing your zsh config
🙃 A delightful community-driven (with 2,500+ contributors) framework for managing your zsh config
Oh My Zsh is an open source, community-driven framework for managing your zsh configuration.
Sounds boring. Let's try again.
Oh My Zsh will not make you a 10x developer...but you may feel like one.
Once installed, your terminal shell will become the talk of the town or your money back! With each keystroke in your command prompt, you'll take advantage of the hundreds of powerful plugins and beautiful themes. Strangers will come up to you in cafés and ask you, "that is amazing! are you some sort of genius?"
Finally, you'll begin to get the sort of attention that you have always felt you deserved. ...or maybe you'll use the time that you're saving to start flossing more often. 😬
To learn more, visit ohmyz.sh, follow @ohmyzsh on X (formerly Twitter), and join us on Discord.
Table of Contents| O/S | Status |
|---|---|
| Android | ✅ |
| FreeBSD | ✅ |
| LCARS | 🛸 |
| Linux | ✅ |
| macOS | ✅ |
| OS/2 Warp | ❌ |
| Windows (WSL2) | ✅ |
zsh --version to confirm), check the following wiki instructions here:
Installing ZSHcurl or wget should be installedgit should be installed (recommended v2.4.11 or higher)Oh My Zsh is installed by running one of the following commands in your terminal. You can install this via the
command-line with either curl, wget or another similar tool.
| Method | Command |
|---|---|
| curl | sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" |
| wget | sh -c "$(wget -O- https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" |
| fetch | sh -c "$(fetch -o - https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" |
Alternatively, the installer is also mirrored outside GitHub. Using this URL instead may be required if you're
in a country like China or India (for certain ISPs), that blocks raw.githubusercontent.com:
| Method | Command |
|---|---|
| curl | sh -c "$(curl -fsSL https://install.ohmyz.sh/)" |
| wget | sh -c "$(wget -O- https://install.ohmyz.sh/)" |
| fetch | sh -c "$(fetch -o - https://install.ohmyz.sh/)" |
Note that any previous .zshrc will be renamed to .zshrc.pre-oh-my-zsh. After installation, you can move
the configuration you want to preserve into the new .zshrc.
It's a good idea to inspect the install script from projects you don't yet know. You can do that by downloading the install script first, looking through it so everything looks normal, then running it:
wget https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh
sh install.shIf the above URL times out or otherwise fails, you may have to substitute the URL for
https://install.ohmyz.sh to be able to get the script.
Oh My Zsh comes with a shitload of plugins for you to take advantage of. You can take a look in the plugins directory and/or the wiki to see what's currently available.
Once you spot a plugin (or several) that you'd like to use with Oh My Zsh, you'll need to enable them in the
.zshrc file. You'll find the zshrc file in your $HOME directory. Open it with your favorite text editor
and you'll see a spot to list all the plugins you want to load.
vi ~/.zshrcFor example, this might begin to look like this:
plugins=(
git
bundler
dotenv
macos
rake
rbenv
ruby
)Note that the plugins are separated by whitespace (spaces, tabs, new lines...). Do not use commas between them or it will break.
Each built-in plugin includes a README, documenting it. This README should show the aliases (if the plugin adds any) and extra goodies that are included in that particular plugin.
We'll admit it. Early in the Oh My Zsh world, we may have gotten a bit too theme-happy. We have over one hundred and fifty themes now bundled. Most of them have screenshots on the wiki (We are working on updating this!). Check them out!
Robby's theme is the default one. It's not the fanciest one. It's not the simplest one. It's just the right one (for him).
Once you find a theme that you'd like to use, you will need to edit the ~/.zshrc file. You'll see an
environment variable (all caps) in there that looks like:
ZSH_THEME="robbyrussell"To use a different theme, simply change the value to match the name of your desired theme. For example:
ZSH_THEME="agnoster" # (this is one of the fancy ones)
# see https://github.com/ohmyzsh/ohmyzsh/wiki/Themes#agnoster[!NOTE] You will many times see screenshots for a zsh theme, and try it out, and find that it doesn't look the same for you.
This is because many themes require installing a Powerline Font or a Nerd Font in order to render properly. Without them, these themes will render weird prompt symbols. Check out the FAQ for more information.
Also, beware that themes only control what your prompt looks like. This is, the text you see before or after your cursor, where you'll type your commands. Themes don't control things such as the colors of your terminal window (known as color scheme) or the font of your terminal. These are settings that you can change in your terminal emulator. For more information, see what is a zsh theme.
Open up a new terminal window and your prompt should look something like this:
In case you did not find a suitable theme for your needs, please have a look at the wiki for more of them.
If you're feeling feisty, you can let the computer select one randomly for you each time you open a new terminal window.
ZSH_THEME="random" # (...please let it be pie... please be some pie..)And if you want to pick a random theme from a list of your favorite themes:
ZSH_THEME_RANDOM_CANDIDATES=(
"robbyrussell"
"agnoster"
)If you only know which themes you don't like, you can add them similarly to an ignored list:
ZSH_THEME_RANDOM_IGNORED=(pygmalion tjkirch_mod)If you have some more questions or issues, you might find a solution in our FAQ.
If you're the type that likes to get their hands dirty, these sections might resonate.
Some users may want to manually install Oh My Zsh, or change the default path or other settings that the installer accepts (these settings are also documented at the top of the install script).
The default location is ~/.oh-my-zsh (hidden in your home directory, you can access it with
cd ~/.oh-my-zsh)
If you'd like to change the install directory with the ZSH environment variable, either by running
export ZSH=/your/path before installing, or by setting it before the end of the install pipeline like this:
ZSH="$HOME/.dotfiles/oh-my-zsh" sh install.shIf you're running the Oh My Zsh install script as part of an automated install, you can pass the
--unattended flag to the install.sh script. This will have the effect of not trying to change the default
shell, and it also won't run zsh when the installation has finished.
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" "" --unattendedIf you're in China, India, or another country that blocks raw.githubusercontent.com, you may have to
substitute the URL for https://install.ohmyz.sh for it to install.
The install script also accepts these variables to allow the installation of a different repository:
REPO (default: ohmyzsh/ohmyzsh): this takes the form of owner/repository. If you set this variable,
the installer will look for a repository at https://github.com/{owner}/{repository}.
REMOTE (default: https://github.com/${REPO}.git): this is the full URL of the git repository clone. You
can use this setting if you want to install from a fork that is not on GitHub (GitLab, Bitbucket...) or if
you want to clone with SSH instead of HTTPS ([email protected]:user/project.git).
NOTE: it's incompatible with setting the REPO variable. This setting will take precedence.
BRANCH (default: master): you can use this setting if you want to change the default branch to be
checked out when cloning the repository. This might be useful for testing a Pull Request, or if you want to
use a branch other than master.
For example:
REPO=apjanke/oh-my-zsh BRANCH=edge sh install.shgit clone https://github.com/ohmyzsh/ohmyzsh.git ~/.oh-my-zsh~/.zshrc Filecp ~/.zshrc ~/.zshrc.origYou can create a new zsh con
Codex CLI errors
Add a copy Button to the setup command.
Oh My Zsh should fix or warn about non-UTF8 locales
Feature: Add Claude Code commands plugin (autocomplete + aliases)
Background completion regeneration (#14000) triggers zcompdump rebuilds when shells start concurrently
Switch default branch to `main` (keep `master` as a mirror)
per-directory-history doesn't save to both global and local
Add zsh-bat into ohmyzsh
omz reload fails with 127 when $commands[zsh] points to a deleted zsh
zcompdump files should prrobably be stored in $ZSH_CACHE_DIR