Zoxide: A Better CD Command
13 comments
·September 23, 2025CopyOnWrite
Does anyone know, how this compares to [autojump](https://github.com/wting/autojump)?
Could not imagine using regular cd for navigating file systems anymore.
Latty
I tried zoxide for a while but I really disliked how it made things fuzzy, and most of the use cases for it I found were 90% solved by using ZSH's history search which I use routinely anyway.
It gives you this potentially constantly shifting set of shortcuts, essentially, and the problem is that means I have to constantly check I did get the result I wanted, and that I haven't accidentally gone to the wrong place. I found that more annoying to me than just using tab completions or history, which are much more predictable.
I can see how someone who has different workflows or environments might find it great though.
tcoff91
It’s just so good.
fzf and zoxide are probably my two most game changing cli tools. They make the terminal feel so good.
tcoff91
I actually made a git worktree aware function called w that wraps zoxide and will basically switch to the main worktree, execute z, and then switch back to the worktree you came from. That way you don’t run into zoxide switching from one worktree to another annoyingly, and new worktrees immediately inherit your zoxide scores. You purge all other worktrees from the zoxide database and use w instead of z inside git repos.
I haven’t used it in a while though because I switched from git to jj.
0x008
care to share?
yerlantemir
super happy to be a super of such an amazing tool, thank you!
mubu
How is this any different from z?
stranges
The main difference is speed (Rust vs shell script)
dag11
This is z, no?
mythz
zoxide alongside fzf, eza, bat and starship were my killer CLI productivity tools I discovered after ditching Windows for Fedora. I have it aliased to `cd` so I don't really notice when I'm using it until moving to a Terminal that doesn't have it.
peauc
I couldn’t live without it now. Very simple yet effective tool
Zizizizz
One of those fundamental work-changing tools. I use it dozens of times a day. It's fantastic
Does anyone know if zoxide has any fancy logic to ignore strings that appear in common prefixes?
For example I have a big ~/src dir where I keep all my code checkouts. If I type 'z src' intending to go to ~/src/foo/bar/src, will it be clever enough to realise that I am referring to the second instance of the string 'src'?
I currently use a Fish port of the original 'z'. It does ignore the common prefix of _all_ matches (so if I only ever used it within my ~/src tree, the problem would disappear) but after that binary exclusion it works exclusively on frecency.