Zed: Pro tips
The setup article in this series got you installed, configured and pointed in the right direction. This one assumes you've been living in Zed for a few weeks, the honeymoon speed rush has settled, and you're ready for the features that don't announce themselves. Zed hides its best ideas behind unassuming names, and the biggest one is first.
Multibuffers are the whole point
If you learn one thing from this article, learn this. When you run a project-wide search in Zed, the results don't open as a list you click through. They open as a multibuffer: one editable surface containing every matching excerpt from every file, stitched together. You edit the results directly, right there, across fifty files if that's what matched, with full multi-cursor support, and saving writes every change back to its source file.
Once this clicks, whole categories of work collapse. Renaming something a refactor tool can't reach: search, edit everywhere at once, save. Reviewing every TODO in the codebase: search, and now they're one scrollable document. And the pattern goes beyond search. The diagnostics view is a multibuffer of every error and warning in the project, editable in place, so you can fix a whole linting sweep without opening a single file by hand. The git diff view is a multibuffer of your changes. Zed's bet is that "a set of places across many files" deserves to be a first-class editing surface, and it's the feature the other editors in this series can't follow it on.
Make the pickers do the walking
The file finder and text search both show live previews as you type, so navigation becomes a matter of glancing rather than committing. Learn the symbol layer too: jump to any function or symbol in the file, or search symbols across the whole project, and keep the outline panel open on wide monitors as a live table of contents. The habit shift is the same one Sublime taught a decade ago: the file tree is for orientation. Navigation happens through fuzzy search, and Zed's implementations are quick enough that you stop thinking of files as things you open and start thinking of code as one continuous place you jump around in.
Tasks, and the keymap that makes them yours
Zed has a task system: define your build, test and dev-server commands once in a tasks.json, run them from the command palette, and rerun the last one with a single binding. Wire your test command to a key and the edit-test loop tightens noticeably. While you're in configuration territory, open the keymap (zed: open keymap) and claim the bindings you use most. Zed's keymap is JSON, supports context-specific bindings (a key can do different things in the editor, the terminal and the agent panel), and ships with VS Code-compatible defaults, so you only need to define your deviations. Ten minutes here repays itself for as long as you use the editor.
Collaboration is built in, and nobody notices
Zed contains a real-time collaboration system: channels you can join with colleagues, shared projects, following another person's cursor around a codebase, voice included. No plugin, no screen-share smearing, actual shared editing on the actual code. It's one of the most complete features in the product and comfortably the least used, partly because remote pairing habits calcified around screen-sharing years ago. If you pair regularly, or you onboard people to unfamiliar codebases, try one session of follow-mode walking someone through the code. Screen-sharing an editor feels primitive afterwards. SSH remoting rounds this out: open a project that lives on a server as if it were local, with your local editor, settings and keymap intact.
Drive the AI, don't ride it
The setup article covered switching the AI features on, off, or somewhere in between. The pro layer is precision. Edit predictions can be constrained rather than binary: keep them eager in the languages where they earn their keep, quieter where they don't, and learn the preview-before-accept flow so suggestions become something you glance at rather than obey. In the agent panel, the discipline that separates useful from chaotic is scope: point an agent at a specific, reviewable task, read the diff it produces like you'd read a junior developer's pull request, and use the ability to run parallel agents for genuinely independent jobs rather than as a way to generate merge conflicts at scale. And remember everything lands as ordinary edits: your review tools are the same multibuffers and git views as always, which is precisely why agent output in Zed stays inspectable. The editor's oldest features turn out to be the guardrails for its newest ones.
The meta-tip
Zed ships updates weekly, and features arrive quietly: pickers gain previews, git panels grow new views, settings migrate into friendlier homes. The genuinely pro habit is skimming the release notes each week, thirty seconds, because in an editor moving this fast the tip that changes your workflow might be four days old. The rest of us find out by accident, months later, usually from someone smug. Read the notes. Be the someone smug.
