Zed vs Neovim: editor setup with OpenCode

The speaker explains why he returned to Zed after rebuilding his Neovim configuration for use with Neovide. His everyday setup uses Tokyo Night and Terminus Nerd Font Mono, while his video profile uses GitHub Dark and Monospace Neon. He says the video theme and font may change later.

Neovide's animated cursor drew him back to Neovim. He walks through his plugin configuration, then describes delays in NeoTree's source selector, particularly its Git status source. These are problems he encountered in his own setup; he acknowledges that a configuration error may have caused them. He felt faster in Zed and preferred having the features he needed built in.

His workflow keeps Zed for projects and Vim or Neovim for individual file edits, including changes to Zed's settings. For AI assistance, he prefers OpenCode in a terminal over Zed's built-in AI panel, and also mentions Claude's CLI. The walkthrough shows how he starts the coding assistant beside his editor, but does not establish whether his models run locally or use a hosted service.

A Space TH key binding opens a terminal on the right. The speaker reports that its action sequence also splits the active file before opening the terminal, an extra step he wants to remove. He attributes this behavior to asynchronous actions in Zed and discusses a possible source-code investigation without committing to it.