I do not dislike Finder. It does its job on macOS, particularly when I need a graphical preview or a familiar drag-and-drop interaction. But for much of my daily work, the important part is not looking at a file. It is getting from the file to the next action.
That is why Yazi has become my primary file manager in the terminal. It feels like a visual commander built for the keyboard: fast directory navigation, immediate previews, and familiar Vim-style movement. It gives me enough visual context to know where I am without pulling me away from the shell.
Finding is only the first half
A conventional file manager often ends its job when I double-click something. In a terminal-first workflow, opening the file is usually the beginning of the next task. My Yazi workflow starts there. I have mapped file-opening actions so I can hand a document to the appropriate macOS application, open text in Helix, and use a shortcut to copy useful information to the Mac clipboard.
That last detail matters more than it sounds. A path discovered in the terminal should be easy to paste into a chat, ticket, document, or Alfred prompt. It should not require a detour through another interface.
I use the same mental model whether I am working with source code, notes, a PDF, or a downloaded file: navigate, inspect, act, return.
Yazi in motion: a short workflow
This looping visual draft follows the same sequence I use in practice: find an architecture PDF in Yazi, open and read it in macOS Preview, return to the terminal, edit code in Helix, and copy a file path to the clipboard. The PDF and application windows are illustrative, not recordings of my actual setup. The point is the handoff: Yazi finds the file, and the appropriate application takes over.
Illustrative demo · 18 seconds · autoplay and loop · muted · locally hosted
Three ordinary examples
Preparing for a customer discussion. I open Yazi in a project directory, move through notes and architecture files using j and k, preview the likely document, and open the PDF in Preview when I need the finished layout. The terminal finds the artifact; macOS displays it where it makes sense.
Reviewing a code change. I locate the relevant Rust, Python, or Elixir file, open it in Helix, and return to the same directory context afterward. I can then run rg, tests, or git diff in the adjacent shell. I am not switching between a file browser, IDE project tree, and a separate command window just to complete a small change.
Sharing a reference. I find a file, copy its path with my Yazi clipboard mapping, and paste it into a message or terminal command. The mapping is a small convenience, but repeated dozens of times it removes meaningful friction. It is also one of those tiny integrations that makes the terminal feel like part of macOS rather than a separate environment.
A few building blocks, not a configuration manual
On macOS, open already knows how to delegate to registered applications, and pbcopy writes to the system clipboard:
open architecture.pdf
printf '%s' "$PWD/architecture.pdf" | pbcopy
hx README.md
These are illustrative shell equivalents of the behaviors I have mapped in Yazi; they are not a claim about the exact contents of my personal keymap.toml or yazi.toml. For a useful integration, the Yazi mapping must correctly quote paths and account for spaces in filenames.
I also like that Yazi does not have to solve every problem itself. If I need to find text inside a hundred files, I can use rg. If I need a fuzzy selection, I can use sk. If I need to process a batch of files, I can use a shell pipeline or a short Python script. And if I need the native application, I can open it.
That is the Unix principle in practice: a file manager is one component of a workflow, not the boundary of the workflow.
Why it stuck
Yazi is quick, its visual structure is easy to understand, and the Vim bindings are already in my hands. It gives me the convenience of a graphical file manager without making me leave my terminal workspace. I can keep my attention on the work rather than the mechanics of finding things.
It also leads naturally to the next experiment. Once Yazi gets me to a file, what should editing feel like? After years of Vim and Emacs, I have been exploring Helix as a fresh, deliberately simpler editing environment.