Need help with oh-my-fish?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

7.7K Stars 664 Forks MIT License 1.8K Commits 67 Opened issues


The Fish Shell Framework

Services available


Need anything else?

Contributors list

The Fishshell Framework

MIT License Fish Shell Version Build Slack Status

Oh My Fish provides core infrastructure to allow you to install packages which extend or modify the look of your shell. It's fast, extensible and easy to use.

Also in  🇪🇸 🇳🇱 🇧🇷 🇷🇺 🇺🇦 🇨🇳

Table of contents


You can get started right away with the default setup by running this in your terminal:

curl -L | fish

This will download the installer script and start the installation. Alternatively, you can download the installer and customize your install:

curl -L > install
fish install --path=~/.local/share/omf --config=~/.config/omf

You can verify the integrity of the downloaded installer by verifying the script against this checksum:

bb1f4025934600ea6feef2ec11660e17e2b6449c5a23c033860aed712ad328c9 install

You can also install Oh My Fish with Git or with an offline source tarball downloaded from the releases page:

# with git
$ git clone
$ cd oh-my-fish
$ bin/install --offline
# with a tarball
$ curl -L > install
$ fish install --offline=omf.tar.gz


install --help
for a complete list of install options you can customize.


  • fish shell, version 2.2 or later
  • git, version 1.9.5 or later

Known Issues

  • Due to a regression bug in fish 2.6 with some terminal emulators, right prompts make the shell unusable. OMF's
    theme features a right prompt, so it's necessary to use an alternative theme until a fix is released. (see #541)

Getting Started

Oh My Fish includes a small utility

to fetch and install new packages and themes.

omf update

Update Oh My Fish, all package repositories, and all installed packages.

  • When called without arguments, update core and all installed packages.
  • You can choose to update only the core, by running
    omf update omf
  • For selective package update, list only the names of packages you wish to update. You may still include "omf" in the list to update the core as well.

omf install

Install one or more packages.

  • You can install packages directly by URL via
    omf install URL
  • When called without arguments, install missing packages from bundle.

omf repositories

Manage user-installed package repositories. Package repositories are where packages come from used by commands like

omf install
. By default the official repository is always installed and available.

omf list

List installed packages.

omf theme

Apply a theme. To list available themes, type

omf theme
. You can also preview available themes before installing.

omf remove

Remove a theme or package.

Packages can use uninstall hooks, so custom cleanup of resources can be done when uninstalling it. See Uninstall for more information.

omf reload

Reload Oh My Fish and all plugins by using

to replace current shell process with a brand new.

This command tries to be as safe as possible, mitigating side-effects caused by

and preventing the reload in case of background processes.

omf new plugin | theme

Scaffold out a new plugin or theme.

This creates a new directory under

$OMF_CONFIG/{pkg | themes}/
with a template.

omf search
-t|--theme / -p|--package

Searches Oh My Fish's database for a given package, theme or both. It also supports fuzzy search, so if you are not sure of the name you can simply

omf search simple

omf channel

Gets or changes the update channel.

Two channels are available by default: the

channel provides stable updates with the latest tagged version of Oh My Fish, and
which provides the latest changes under development. The update channel currently set determines what version
omf update
will upgrade to.

omf doctor

Use to troubleshoot before opening an issue.

omf destroy

Uninstall Oh My Fish.


Oh My Fish installer adds a snippet to fish's user config files (

) which calls OMF's startup code.

Notice that the scripts in that directory are sourced in the order that the filesystem sees them, and so it may be necessary to prefix your script files with ordering numbers.

For example:
will take precedence over the
snippet. So if
depends on plugins managed by OMF, consider renaming the script file to

Similarly, to make sure that a script runs before
, you may prefix it with
. Alternatively,
may be used.


Every time you open a new shell, the startup code initializes Oh My Fish installation path and the config path (

by default), sourcing the
script afterwards, which autoloads packages, themes and your custom init files.

For more information check the FAQ.



directory represents the user state of Oh My Fish. It is the perfect candidate for being added to your dotfiles and/or checked out to version control. There you can find three important files:
  • theme
    - The current theme
  • bundle
    - List of currently installed packages/themes
  • channel
    - The channel from which OMF gets updates (stable / dev)

And you may create and customize these special files:

    - Custom script sourced after shell start
    - Custom script sourced before shell start
    - Custom key bindings where you can use the
    command freely

Setting variables in

One of the most common startup commands used in
is variables definition. Quite likely, such variables need to be available in any shell session. To achieve this, define them globally. For example:
# Golang developers might need this one
set -xg GOPATH $HOME/gocode

Python developers otherwise


About the bundle

Every time a package/theme is installed or removed, the

file is updated. You can also edit it manually and run
omf install
afterwards to satisfy the changes. Please note that while packages/themes added to the bundle get automatically installed, a package/theme removed from bundle isn't removed from user installation.

Older fish versions

In fish 2.2, there is no

directory, so the startup code has to be placed in the fish config file (

It's highly recommended that your custom startup commands go into
file instead of
, as this allows you to keep the whole
directory under version control.

If you need startup commands to be run before Oh My Fish begins loading plugins, place them in
instead. If you're unsure, it is usually best to put things in

Creating Packages

Oh My Fish uses an advanced and well defined plugin architecture to ease plugin development, including init/uninstall hooks, function and completion autoloading. See the packages documentation for more details.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.