Awesome, thank you. I've been trying it for the last few minutes, really liking it. Pretty impressed with how well it works using ollama + qwen3:32b

Two nitpicks:

1) the terminal is not picking up my regular terminal font, which messes up the symbols for my zsh prompt (is there a way to fix this?)

2) the model, even though it's suggesting very good edits, and gives very precise instructions with links to the exact place in the code where to make the changes, is not automatically editing the files (like in the video), even though it seems to have all the Write tools enabled, including editing - is this because of the model I'm using (qwen3:32b)? or something else?

Edit: 3rd, big one, I had a js file, made a small 1 line change, and when I saved the file, the editor automatically, and without warning, changed all the single quotes to double quotes - I didn't notice at first, committed, made other commits, then a PR - that's when I realized all the quotes changes - which took me a while to figure out how they happened, until I started a new branch, with the original file, made 1 change, saved and then I saw it

Can this behavior be changed? I find it very strange that the editor would just change a whole file like that

1. You can specify your terminal font via terminal.font_family in zed settings.json

2. Not sure.

3. For most languages, the default is to use prettier for formatting. You can disable `format_on_save` globally, per-language and per project depending on your needs. If you ever need to save without triggering format ("workspace: save without formatting").

Prettier is /opinionated/ -- and its default is `singleQuote` = false which can be quite jarring if unexpected. Prettier will look for and respect various configuration files (.prettierrc, .editorconfig, via package.json, etc) so projects can set their own defaults (e.g. `singleQuote = true`). Zed can also be configured to further override prettier config zed settings, but I usually find that's more trouble than it's worth.

If you have another formatter you prefer (a language server or an external cli that will format files piped to stdin) you can easily have zed use those instead. Note, you can always manually reformat with `editor: format` and leave `format_on_save` off by default if that's more your code style.

- https://zed.dev/docs/configuring-zed#terminal-font-family

- https://zed.dev/docs/configuring-zed#format-on-save

- https://prettier.io/docs/configuration

- https://zed.dev/docs/languages/yaml#prettier-formatting

- https://zed.dev/docs/configuring-zed#formatter

Thank you for the excellent and informative reply. Will try it out

It would be nice for prettier to throw a user warning before making a ton of changes on save for the first time, and also let them know where they can configure it

Just in case, this worked for me on a Mac with agnoster theme for zsh:

  "terminal": {
    "font_family": "Meslo LG M DZ for Powerline",
    "font_size": 13,
    "font_fallbacks": ["Meslo LG M for Powerline"]
  }