They use backend configurable at environment variable ZED_PREDICT_EDITS_URL https://github.com/zed-industries/zed/blob/2f734cbd5e2452647... , but I don't know if the /predict_edits/v2 endpoint is something some projects provide or not.

At least the model is available and interacting with it seems simple, so it's probably quite realistic to have an open/locally runnable version of it. The model isn't very big.

yeah, i'd like to be able to run it locally. it should fit well onto my 12gb gpu

The model is based on Qwen2.5-Coder-7b it seems. I currently run some quantized variant of Qwen2.5-Coder-7b locally with llama.cpp and it fits nicely in the 8GB VRAM of my Radeon 7600 (with excellent performance BTW), so it looks like it should be perfectly possible.

I would also only use Zeta locally.

Are you happy with the speed with your 8GB GPU?

> a private key or API key could get sent, right?

You can disable this feature on a per-file basis, here’s the relevant setting: https://github.com/zed-industries/zed/blob/39c9b1f170cd640cd...

Sending files to a remote server is never something that should need to be disabled, this must be an opt-in or it's time for a fork.

It is opt in. You have to manually sign in to Zed and enable the feature.

Agreed. The predict edit feature needs to be actively enabled before it'll do anything. And once it's enabled, it won't send up your private keys or environment variables. If their filename matches a glob in this list, or a list you configure.