My primary IDE at the moment is zed. It has a nice feature set which I feel captures the upsides of both VSCode and Vim in a single IDE. It seems to also have a sane take on AI in the development workflow.
Zed uses CRDTs: https://zed.dev/blog/crdts. I have used it for remote pairing between people in the USA and in Australia and it worked exactly as advertised. It is an amazing feature. I have tried pair programming across those two continents with classical approaches of controlling the other person's screen remotely and it is simply too laggy to be practical.
Zed has clean AI integrations that allow you to easily supply context to the LLMs including whole files and individual lines. I like this because it is promise free. It's not a UX of what could work one day, but a practical UX of what works today, where you supply all the context manually in the conversation you are having. The power of Zed's UX is that it makes that manual interactions easy with keybindings.
Settings
I am committing my settings to github: https://github.com/aegatlin/dotzed
Vim settings go in keymap.json. I was confused about this at first and thought they were supposed to be in settings.json next to the vim_mode: true setting.
Useful commands
Go to definition in split window
In Vim mode: ctrl-w g d (https://zed.dev/docs/vim#pane-management)
For type definition it is ctrl-w g D
In normal mode: alt f12 (https://zed.dev/docs/key-bindings#editor)
For type definition it is alt ctrl f12
Toggle zoom
shift + escape no matter what panel/pane you are in this will “zoom” it, which means make it full screen. It works with terminals, split window editors, project directory, etc. It is listed with the other global key-bindings
Code completions
https://zed.dev/docs/completions
“Code completions” in zed are from LSPs while “inline completions” are from what they call “external APIs”, but which are essentially 3rd party AI completions.
Tasks
There are a variety of zed-provided shell variables for tasks.
https://zed.dev/docs/tasks#variables
There are a lot of capabilities here. One that I’ve never seen before is a concept of a one-shot task. You can just type a shell command and hit opt+enter to run it. It will show up in your task list for rerunning for the duration of your session. It works with the zed shell variables as well. For example, if you are working in Nodejs with a Jest test suite and you are working on a particular file that you don’t want as a permanent task you can create a oneshot task of npm run test —- $ZED_FILE and it will create a task for just that file. (Shell variable expansion does not let you reuse $ZED_FILE reactively, it will create a task for just that test file).