Framework
oh-my-fish/oh-my-fish avatar
oh-my-fish/oh-my-fish

oh-my-fish puts an unmaintained warning above its own install command

The Fish Shell Framework

11,420 stars802 forksShellMIT

At a glance

What is it?
oh-my-fish is the package and theme framework for the fish shell, installed by piping a script from the master branch into fish. Its README opens by saying the maintainers have run out of steam and that some themes and packages are broken, which is the first thing anyone adopting it has to weigh.
Who is it for?
Adopt oh-my-fish only if you already live in fish and want its theme catalog, because the project states it is unmaintained, some themes and packages are broken, and the code is due a significant overhaul. Skip it for a team that needs a support commitment.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 47 days ago.
What is it written in?
Mainly Shell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • oh-my-fish/oh-my-fish11,420 ★ · +29
Star history
Repository2026-09-222026-11-15
oh-my-fish/oh-my-fish11.4k11.4k

29 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README opens with an unmaintained warning, then an install command

The first block on the project's front page is a warning, not a feature list. It states that Oh My Fish has been unmaintained for years, that certain parts may not work for you, that a few themes and packages are currently broken, and that the code is due a significant overhaul. It says the current set of maintainers have ran out of steam, and invites people who want to take over to email the project group.

What follows describes the framework as core infrastructure for installing packages that extend or modify the look of your shell, fast, extensible and easy to use.

Two sets of facts sit next to each other. The repository was last pushed to on 2026-09-30, and the Version 8 tag was cut on 2026-04-07, six years after Version 7 in 2020. The code is still being touched, and the project's own description of it is that nobody is looking after it. Plan on reading and fixing what breaks rather than filing an issue and waiting. The documentation also exists in six translations under docs/, in es-ES, nl-NL, pt-BR, ru-RU, uk-UA and zh-CN.

The default install pipes a script from master straight into fish

Installation is one line, and it runs a script fetched from the master branch of the repository rather than from a tagged release:

fish
curl https://raw.githubusercontent.com/oh-my-fish/oh-my-fish/master/bin/install | fish

That command downloads the installer and starts it. Read it as a pipe from the network into your shell interpreter: whatever is on that branch at that moment runs with your permissions, which is why the next section matters.

If you want to keep the installer around and decide where things land, download it first and pass the two paths yourself:

fish
curl https://raw.githubusercontent.com/oh-my-fish/oh-my-fish/master/bin/install > install
fish install --path=~/.local/share/omf --config=~/.config/omf

`--path` sets the installation directory and `--config` sets the config directory, and the config path defaults to `~/.config/omf`. The installer also takes `--help`, which is where you find the complete list of options.

bin/install.sha256 lets you check the script, and --offline skips the network

The repository publishes a checksum for the installer, so the pipe-to-fish step can be checked before you run it:

bash
curl -sL https://raw.githubusercontent.com/oh-my-fish/oh-my-fish/master/bin/install.sha256 | shasum -a 256 --check

Verify against that file before running the download, and remember what it protects you from: both the script and its checksum come from the same unpinned branch, so a change on master changes both.

For a machine with no network at all, `--offline` behaves like `--local-source` and skips fetching plugins, and you can run `omf install` afterwards to get them. For a container image the project builds its own, starting from a fish 4.8.1 base image and running the installer non-interactively:

dockerfile
FROM ohmyfish/fish:4.8.1

COPY . /src/oh-my-fish

RUN fish /src/oh-my-fish/bin/install --local-source --noninteractive --yes

The `--noninteractive --yes` combination is the one to copy if you script the install, because it stops the installer waiting for an answer it will never get.

fish 3.0 and git 1.9.5 are the only stated requirements

The requirements section lists two things: the fish shell at version 3.0 or later, and git at version 1.9.5 or later. Nothing else is named, and no distribution is named either.

Because fish is a prerequisite, install it first; on macOS, where fish is not the default shell and often not installed at all, that is the first thing to check.

Git is listed as a requirement alongside fish, and `omf install` accepts a name, a URL or a `user/repo` GitHub repository.

The default theme's right prompt breaks on the fish 2.6 regression

There is a known issue, and it is specific. A regression bug in fish 2.6, combined with some terminal emulators, makes right prompts unusable, to the point where the shell cannot be worked in. Oh My Fish's `default` theme features a right prompt, so on such a setup you have to switch to a different theme until a fix is released. The issue is tracked as number 541 in the repository.

The awkward part is that this describes fish 2.6 while the requirements ask for fish 3.0 or later, so a correctly installed system is supposed to be outside the blast radius. The README's advice for anyone affected is to use an alternative theme until a fix is released.

conf.d is sourced in filesystem order, so filenames decide who wins

Oh My Fish works by dropping a snippet into fish's own user config directory, `~/.config/fish/conf.d/`, and that snippet calls the framework's startup code. fish sources the scripts in that directory in whatever order the filesystem returns, which is the whole mechanism people trip over.

Ordering is therefore expressed in file names. A script called `a_script.fish` takes precedence over the `omf.fish` snippet, because `a` sorts first. If that script depends on plugins the framework manages, rename it to `xx_a_script.fish` so it loads after them. To run something before the framework instead, prefix it with `00_`, or use `~/.config/omf/before.init.fish`.

On every new shell, startup code sets the installation path and the config path, `~/.config/omf` by default, then sources `init.fish`, which autoloads packages, themes and your own init files. `$OMF_CONFIG` holds the user state and is the directory to keep in your dotfiles repository, since that is what `omf install` with no arguments uses to reinstall missing packages from your bundle.

omf reload replaces your shell process, and refuses when jobs are running

The command surface is small and each command does one thing. `omf update` refreshes the framework, its package repositories and installed packages; `omf update omf` limits it to the core. `omf install` takes a name, a URL or a user/repo pair, and with no arguments it installs whatever is missing from your bundle. `omf repositories list|add|remove` manages extra package sources, with the official packages-main repository always present. `omf list` shows what is installed, `omf theme <theme>` applies one and lists the available themes when given no argument, and `omf remove <name>` uninstalls, with `repo` as the name for something installed from a user/repo pair.

`omf reload` is the one to understand before you type it. It uses `exec` to replace the current shell process with a brand new one, and the documentation says it mitigates the side effects of `exec` and refuses to reload when background processes are running. That refusal is a feature: your jobs survive instead of dying with the old process.

`omf doctor` is there for before you open an issue, `omf destroy` uninstalls the framework, and `omf new plugin|theme <name>` scaffolds a new directory under `$OMF_CONFIG/{pkg | themes}/` from a template. `omf search` looks in the package and theme database with `-t|--theme` or `-p|--package`, and accepts a partial name such as `simple` because it is a fuzzy search. `omf channel` sets where updates come from: `stable` gives the latest tagged version, `dev` gives the latest changes, and whichever is set decides what `omf update` upgrades to.

omf destroy is the exit, and the alternative is a hand-written conf.d

Because the framework's entire presence in your shell is one snippet in `~/.config/fish/conf.d/` plus your own `$OMF_CONFIG`, getting out is a documented command. `omf destroy` uninstalls Oh My Fish.

That is also the honest alternative to adopting it: keep your own scripts in `~/.config/fish/conf.d/` and your own init file, and skip the framework entirely. The approach differs in what it gives up. Hand-written config has no theme catalog to browse, no `omf search` over a package database, no `omf update` to run, and no channels to reason about, and it cannot break when a package repository changes underneath you. What you gain is that nothing about your prompt depends on someone else's repository, which matters in a project where a broken theme means an unusable shell.

The reverse also holds. If you want the catalog and accept the breakage, the framework saves you writing and maintaining prompt code by hand.

Editorial conclusion

Adopt oh-my-fish only if you already live in fish and want its theme catalog, because the project states it is unmaintained, some themes and packages are broken, and the code is due a significant overhaul. Skip it for a team that needs a support commitment. If you install it anyway, take the script-based route the README documents, and keep your config in $OMF_CONFIG.

Frequently asked questions

what is oh my fish

oh-my-fish is the framework for the fish shell. It provides the infrastructure for installing packages that extend or modify the look of your shell, and it ships the omf command to fetch and install packages and themes.

how to install oh my fish

Run `curl https://raw.githubusercontent.com/oh-my-fish/oh-my-fish/master/bin/install | fish`, which downloads the installer script and starts the installation. You need the fish shell at version 3.0 or later and git at version 1.9.5 or later, and `install --help` lists every option.

install oh my fish ubuntu

The README's installation section gives one set of instructions rather than per-distribution ones. Install fish 3.0 or later and git 1.9.5 or later, then download the installer and point it at your own directories with `fish install --path=~/.local/share/omf --config=~/.config/omf`, or use `--offline` on a machine with no network access and fetch plugins later with `omf install`.

Official sources

  1. Issues
  2. License: MIT
  3. oh-my-fish/oh-my-fish on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/oh-my-fish-oh-my-fish.svg)](https://hysenlabs.com/projects/oh-my-fish-oh-my-fish)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/oh-my-fish-oh-my-fish.svg)](https://hysenlabs.com/projects/oh-my-fish-oh-my-fish)

Was this useful?