-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add build time options to disable ML/AI features #6756
Comments
I have created a fork of Zed that has compile time features (switches) to enable/disable (with all disabled by default) the assistant, collaboration (sign in, etc), and copilot. You can find the branch here |
@haze can you make a PR to add this to this repo? If you already have then referencing this issue can help more people like myself know there is already a PR |
I guess because the main devs are pro-AI the AI default would need to be "On" but it would still be great to be able to build packages with it turned off so that people have the option of either choice. |
@Pi-Cla Sorry, but I'm not interested in maintaining a permanent fork with these changes applied. It's already wildly out of date, and took a considerable amount of effort just to use. I also don't think I properly removed some elements. I'd try and petition the Zed people to add this, but I can't say I see them buckling, since you can disable them via hiding the UI elements. |
I’d love to see a version with AI/ML disabled. It’s what is single handedly holding me personally back from giving this a shot to replace VS Codium |
I was about to try Zed but the paragraph about AI made me choose not to. An option to disable it completely is absolutely necessary. |
ya, Zed without AI will be awseome. Maybe make it as opt-in extension. |
I really like this idea especially as a For now I don't see that current so-called "AI"s are very useful. They may be used as a smart snippet tool, but nothing more. Fine it may work better in other languages, but if we give such argument then do we still talking about AI - a computer intelligence that would learn, learn and decides to kill us? No, it's just a tool, very complex one, but still far away from a true "AI" (as people see it). Currently if AI does not have a good language support it may make a very trivial mistakes like it may even have a problem with understanding types. There are really number of examples why people don't see it useful in their environments. |
Yea, I had to search for the options of how to disable all of those AI/Assistant/ML/Collab/Chat features. So annoying. |
+1 from me; I would absolutely love an offline version |
+1, this is what's keeping me from using Zed over VSCodium On macOS, there's a nice application called Lulu that allows preventing all network access for an application, but this would likely cause issues with language servers. I haven't tried this yet but it's worth a shot. |
I would also like an auto-opt-out-of-AI-features option. Zed's advantages for me are that it's faster than VSCode and it has the file drag-and-drop interface that Sublime Text refuses to implement, but for me the AI stuff is all downside from a security, licensing, and ethical perspective. I don't want to have to be watching out for being silently opted-in to future AI features. |
Every couple of months I see Zed recommended, but this (and the lack of an official Windows build) prevent me from using it. Many projects, e.g. Gentoo and NetBSD, have an outright ban on AI generated code. If a Zed user wants to contribute to such projects, or they work for company that has policy against using AI they have no choice but to use a different code editor/IDE. Even in (now very pro-AI) VS Code any AI aspects are contained in extensions which can be removed/disabled completely or per project. If Zed is to be the ultimate code editor for every use case, then ensuring it remains usable in situations where AI is not allowed (for whatever reason) is an important thing to support. |
I see on the roadmap that "embracing AI" is on the list. I understand that for some majority of developers this is something they do want to see explored. For another chunk of us (that I sometimes fall in, sometimes not depending on the project) there are fundamental issues with having any AI input into our coding process. For some users/projects this is an ethical boundary, for others just a licensing issue, etc.
I firmly believe that to be a really robust editor any features that attempt to make use of ML/AI tooling they should be optional. This should probably include both a build-time option so that the project can be built from source with no AI related dependencies even needed and no features enabled. The existing setting
assistant = false
only disables the related UI elements at run time. The build time variant should actual build a binary where these things are not even available at all, not just hidden.In conjunction with this the related features could possible be stubbed in some way so that future 3rd party plugins or user coded automation can't accidentally access them even though the UI elements are hidden.
The text was updated successfully, but these errors were encountered: