zoxide: A Frequency-Based cd Replacement That Remembers Where You Go
GitHub describes it as A smarter cd command. Supports all major shells.. The repository metadata lists Rust as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- zoxide is a Rust-based cd replacement that ranks directories by usage frequency and lets you jump with fuzzy matches. It supports all major shells and is easy to install, but its ranking model and dependency on a separate binary may not suit every workflow.
- Who is it for?
- Adopt zoxide if you spend most of your time in a small set of deep or hard-to-type directories and want a fast, cross-shell jump command with minimal setup. Avoid it if you need deterministic path resolution or if you work in environments where installing a separate binary is impossible.
- 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 8 days ago.
- What is it written in?
- Mainly Rust, 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.
Star history
- ajeetdsouza/zoxide40,599 ★ · +1,965
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| ajeetdsouza/zoxide | 38.6k | 40.6k |
1,965 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The Problem: cd Is Slow When You Have Deep or Repeated Paths
The standard cd command only accepts a literal path. If you work in a project nested five levels deep, you type that full path every time, or you rely on shell history and aliases. zoxide solves this by remembering which directories you visit most often and letting you jump to them with a partial match. It is inspired by z and autojump, which have the same goal but with different implementations. The intended user is someone who lives in a terminal and repeats the same handful of directories daily. The README shows the core interaction: `z foo` changes to the highest ranked directory matching foo, and `z foo bar` matches both patterns in the same path. That is the entire pitch, and it is a good one for a specific pain point.
How the Ranking and Matching Work
The README points to a separate page for the matching algorithm, zoxide ranks directories by frequency of use, so the more you visit a path, the higher it ranks. The command `z foo` picks the highest ranked directory that matches the string foo. Multiple arguments narrow the match: `z foo bar` requires both foo and bar to appear in the path. The syntax also supports special cases: `z foo /` matches a subdirectory starting with foo, `z ~/foo` works like a regular cd, `z foo/` changes to a relative path, `z ..` goes up one level, and `z -` returns to the previous directory.
Getting It Running: Installation and Shell Integration
Installation is straightforward on most platforms. The recommended method is a curl script: `curl -sSfL https://raw.githubusercontent.com/ajeetdsouza/zoxide/main/install.sh | sh`. Alternatively, you can use a package manager. On Linux, examples include `cargo install zoxide --locked`, `conda install -c conda-forge zoxide`, `nix-env -iA nixpkgs.zoxide`, `pacman -S zoxide`, and `dnf install zoxide`. macOS supports `brew install zoxide` and `port install zoxide`. Windows uses `winget install ajeetdsouza.zoxide`. The README also notes that Debian, Ubuntu, Parrot OS, and Raspbian packages are struck through, meaning they are not available, so users on those systems must use the script or another source. The README describes installation as four steps, the first being to install the binary. It lists `zi foo` for fzf-based selection, and tab completions only for bash 4.4+, fish, and zsh.
Interactive Features: fzf Selection and Tab Completions
Beyond plain jumping, zoxide offers two interactive modes. The `zi` command opens an interactive selection using fzf, so you can visually choose from a list of matching directories. The README shows `zi foo` as the example. There is also a tab completion feature: typing `z foo<SPACE><TAB>` displays interactive completions, but only in bash 4.4+, fish, and zsh. That means PowerShell and older bash versions do not get this feature, which is a real limitation for some users. The fzf dependency is not bundled; you need to have fzf installed separately for `zi` to work. This is a good example of a feature that looks simple but carries an external dependency.
A Genuine Limitation: Ranking Can Surprise You
The frequency-based ranking has a failure mode. If you have two directories that both match the same pattern, zoxide always picks the higher ranked one, even if you wanted the other. For example, if you have `/home/user/projects/alpha` and `/home/user/projects/beta`, typing `z pro` will jump to whichever has the higher visit count. If you meant the other one, you must type a longer pattern. This is fine for the common case, but it makes zoxide the wrong tool for scripts or for users who need deterministic behavior.
Alternative: Plain cd with Shell History or a Fuzzy Finder
The obvious alternative is to skip zoxide and use your shell's built-in history or a fuzzy finder like fzf alone. With fzf, you can bind a key to search and cd into any directory from your history or a file list, giving you full control over the match. The difference in approach is that fzf shows you all matches and lets you pick, while zoxide picks for you based on frequency. That is a meaningful trade-off: zoxide is faster because you do not see a list, but fzf is more predictable because you see exactly what you are choosing. Another alternative is to write a shell function that uses `cd` with globbing or `find`, but that is less ergonomic. If you already use fzf, the `zi` command in zoxide gives you the best of both, but it still depends on the same ranking data underneath.
Maintenance, License, and Upgrade Cost
zoxide is written in Rust and released under the MIT license, which is permissive and has no copyleft obligations. The repository was last pushed on 2026-11-01 and is not archived. Recent releases are 0.10.0 in July 2026, 0.9.9 in January 2026 and 0.9.8 in May 2025. Upgrading is typically a matter of reinstalling via your package manager or the install script. The main maintenance cost is the database file that zoxide maintains; you need to be aware of where it lives and whether it grows unbounded. The license is clean, so there are no legal blockers for commercial use, but you should still verify the exact terms if you plan to redistribute it.
Editorial conclusion
Adopt zoxide if you spend most of your time in a small set of deep or hard-to-type directories and want a fast, cross-shell jump command with minimal setup. Avoid it if you need deterministic path resolution or if you work in environments where installing a separate binary is impossible. Before adopting, verify that your shell's completion features (bash 4.4+, fish, zsh) are enabled, and check that the install script or package manager you choose matches your platform, since Debian, Ubuntu, Parrot OS, and Raspbian packages are explicitly marked as unavailable. Test the matching algorithm with your actual directory names to ensure it ranks them as you expect.
Frequently asked questions
What is zoxide?
It is a cd replacement written in Rust that remembers which directories you use most frequently and jumps to them in a few keystrokes. The README describes it as a smarter cd command inspired by z and autojump, and it says it works on all major shells.
How do I install zoxide on macOS?
macOS is listed with package managers rather than a preferred script: brew install zoxide, port install zoxide, conda install -c conda-forge zoxide, nix-env -iA nixpkgs.zoxide, or cargo install zoxide --locked. The same install script used on Linux is offered as the alternative.
How do I install zoxide on Ubuntu?
The Ubuntu row in the install table is struck through, as are the Debian, Raspbian and Parrot OS rows, so apt install zoxide is not offered there. The install script or a source build with cargo install zoxide --locked are the routes the table leaves you.
How do I use zoxide day to day?
Type z plus a fragment to move to the highest ranked matching directory, add a second fragment to require both words, and add a trailing slash to cd into a relative path. z also accepts ordinary cd forms such as z .. and z -, and zi opens an interactive picker built on fzf.
How does zoxide compare with autojump and z?
The README names z and autojump as its inspiration without spelling out the differences.
Is zoxide safe to use?
The step worth reading before running anything is the install line, since the recommended Linux route pipes a script fetched from GitHub straight into sh.
Official sources
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.
[](https://hysenlabs.com/projects/ajeetdsouza-zoxide)Star history chart for your README
[](https://hysenlabs.com/projects/ajeetdsouza-zoxide)Was this useful?