-
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
Description
Reproduction steps
Starting zed with ZED_PREDICT_EDITS_URL:
ZED_PREDICT_EDITS_URL="https://my-own-server.com/prefix/autocomplete/predict_edits" zed
This was critical for bring-your-own models (privacy/enterprise/self-hosted experimentation).
Current vs. Expected behavior
I am asking you to restore ZED_PREDICT_EDITS_URL feature.
What changed / regression
It looks like support for ZED_PREDICT_EDITS_URL was removed in Feb 2026 (commit c430681 in #48541).
c430681211#diff-2fa2fa10ee089adc3c13d5a47815ae34b557985d490607bbc2b95c63ab07c468L645-L648
This means there’s currently no way to send predict-edits requests to a custom URL.
Related context
- Auth-free / custom endpoint support for AI autocomplete was recently added (thank you) - Enable Zeta edit predictions with custom URL without authentication #43236
- Similar discussion in Edit Predictions: without ZED_PREDICT_EDITS_URL cannot set local backend #30308, including: “happy to restore ZED_PREDICT_EDITS_URL until we offer a more first-class way of bringing your own edit prediction model.”
- Brining my own model unlocks security concerns for me
Why the replacement doesn’t cover this
ZED_ZETA_FORMAT / ZED_ZETA_MODEL allows experimenting with format/model while still using the standard server raw endpoint, but it does not let me route requests to my own server. My requirement is specifically custom URL routing for edit predictions.
Claude summary snippet:
The send_raw_llm_request still accepts a custom_url parameter, but the only call site in zeta2.rs:120-123 always passes None. No env var or setting populates it anymore.
Here's what you can still customize via env vars:
┌───────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Env var │ What it does │
├───────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ZED_ZETA_FORMAT │ Activates the raw endpoint path and selects a prompt format (e.g. v0131_git_merge_markers_prefix) │
├───────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ZED_ZETA_MODEL │ Overrides the model ID sent to the raw endpoint │
├───────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ZED_ACCEPT_PREDICTION_URL │ Custom URL for the acceptance tracking callback only │
└───────────────────────────┴───────────────────────────────────────────────────────────────────────────────────────────────────┘
But all prediction requests go to Zed's own LLM server (/predict_edits/raw or /predict_edits/v3) — there's no way to redirect them to your own endpoint anymore.
If you need this capability back, you'd need to re-add a ZED_PREDICT_EDITS_URL env var check. The plumbing is still there (send_raw_llm_request accepts custom_url: Option<Arc<Url>>), so the change would be small — just populate it from the env in zeta2::request_prediction_with_zeta2 instead of always passing
None.
Request / acceptance criteria
Please restore ZED_PREDICT_EDITS_URL (even if documented as “advanced/unsupported”) so that:
- When set, edit prediction requests are sent to the provided URL.
- This works with the new prompt/model config (Zeta format/model env vars) if applicable.
Could you take a look please?
Zed version and system specs
version with ZED_PREDICT_EDITS_URL supported:
Zed 0.222.3
59dfdea
0.223.3+stable.152.59dfdea1697030fd39de6c92172ff192d013a984
removed since v0.224.0-pre.
Attach Zed log file
Zed.log
Relevant Zed settings
settings.json
Relevant Keymap
ZED_PREDICT_EDITS_URL="https://my-own-server.com/prefix/autocomplete/predict_edits"
(for AI issues) Model provider details
No response
If you are using WSL on Windows, what flavor of Linux are you using?
None