Can you say more about why you removed .... Should we rephrase the comment instead of removing all other language servers (so that the documentation matches Zed's documentation in https://github.com/zed-industries/zed/pull/50662/changes)

I removed the "..." because while its underlying logic (enabling all remaining registered adapters) hasn't changed, Zed's registry behavior has. Previously, adapters like pylsp and pyright and ty were lazy-loaded and didn't appear in the registry unless explicitly invoked. Because of this, a configuration like ["ty", "!basedpyright", "..."] would coincidentally only enable ruff, making the old documentation’s claim that ... meant "keep defaults" appear correct in practice.

However, after the registry logic change in zed-industries/zed#50662, all five Python adapters are now registered upfront. This means keeping the ellipsis would now result in an effective configuration of ["ty", "!basedpyright", "ruff", "pylsp", "pyright"], spawning redundant language servers that users don't actually want. While Zed’s own documentation might retain the "..." to explain the feature's mechanics, I believe our documentation for ty should prioritize providing a clean, "copy-pasteable" configuration. By removing the ellipsis, we ensure that users get exactly what they expect—ty enabled and basedpyright disabled—without any unintended side effects or performance overhead from extra LSPs.

In case I wasn't clear, here's an example from the main Zed docs that should give you a better idea of what I mean about the "..."

I removed the "..." because while its underlying logic (enabling all remaining registered adapters) hasn't changed, Zed's registry behavior has. Previously, adapters like pylsp and pyright and ty were lazy-loaded and didn't appear in the registry unless explicitly invoked. Because of this, a configuration like ["ty", "!basedpyright", "..."] would coincidentally only enable ruff, making the old documentation’s claim that ... meant "keep defaults" appear correct in practice.

However, after the registry logic change in zed-industries/zed#50662, all five Python adapters are now registered upfront. This means keeping the ellipsis would now result in an effective configuration of ["ty", "!basedpyright", "ruff", "pylsp", "pyright"], spawning redundant language servers that users don't actually want. While Zed’s own documentation might retain the "..." to explain the feature's mechanics, I believe our documentation for ty should prioritize providing a clean, "copy-pasteable" configuration. By removing the ellipsis, we ensure that users get exactly what they expect—ty enabled and basedpyright disabled—without any unintended side effects or performance overhead from extra LSPs.

Thank you for explaining this! Finally I understand why the behaviour of "..." changed recently.

Can you say more about why you removed .... Should we rephrase the comment instead of removing all other language servers (so that the documentation matches Zed's documentation in https://github.com/zed-industries/zed/pull/50662/changes)

Note that https://github.com/zed-industries/zed/pull/51427/changes was just merged, which makes Zed's docs on "..." more clear that it enables all other languages servers.

If removing "...", then also remove !basedpyright entirely. There's really no point in leaving it.

You're absolutely right. I had a misunderstanding of how the configuration merges: I previously thought that servers not explicitly mentioned would still follow the default settings, which is why I didn't include "ruff" and thought I needed "!basedpyright".

Since I actually want to keep "ruff" enabled alongside "ty", I should explicitly list both and remove the unnecessary "!basedpyright" entry. I'll update the PR after some manual testing. Thanks for pointing this out!