fzd

Interactive terminal directory explorer that cd's your shell.

fzd opens a fuzzy, keyboard-driven TUI for browsing directories. It draws its UI to stderr and prints only the chosen absolute path to stdout, so a tiny shell wrapper can capture that path and run the real cd in your current shell.

Install

Pick whichever ecosystem you already live in — every channel ships the same binary.

Shell integration

Because a child process can't change its parent shell's directory, fzd prints the picked path and a wrapper does the cd. For fish, source the bundled function:

source /path/to/shell/fzd.fish

Then:

fzd            # browse from the current directory
fzd ~/code     # browse starting somewhere else
fzd --jump     # jump straight to frecent / bookmarked dirs
fzd -j         # short form

Usage

fzd [OPTIONS] [PATH]

Arguments:
  [PATH]  Directory to start in (defaults to the current directory)

Options:
  -j, --jump        Start directly in jump mode (frecent + bookmarked dirs)
  -a, --all         Show hidden (dot) files from the start
      --print-only  Do not record the accepted directory in the frecency store
      --check-update  Check GitHub for a newer release, then exit
      --update        Download the latest GitHub release and replace this binary
      --force         With --update, replace a package-manager-managed binary
  -h, --help        Print help
  -V, --version     Print version

Updating

fzd --check-update compares your installed version against the latest GitHub release and prints whether you're current, without opening the TUI.

fzd --update goes further: it downloads the release binary for your platform and swaps it in over the running executable. This is meant for the raw-binary install (the curl | bash script or a manual download). If fzd was installed through a package manager, --update stops and points you at the right command (cargo install fzd --force, npm update -g fzd, brew upgrade fzd, and so on). Pass --force to self-replace anyway.

Development

This repo ships a Nix flake and a pinned Rust toolchain:

nix develop          # enter the dev shell (or `direnv allow` with the .envrc)
cargo run            # run locally
cargo build --release

Releasing

Releases are fully automated from Conventional Commits via semantic-release in GitHub Actions. A feat:/fix:/feat!: commit on main computes the next version, builds binaries for six platforms, and publishes to crates.io, npm, PyPI, and GitHub Releases in one run. See .github/workflows/release.yml.

License

MIT