Privacy hardening (no phone-home). Chokepoint cuts that kill the behavior while
keeping surrounding code compiling (collab/CRDT retained for later self-hosting):
A — sign-in removed:
- main.rs authenticate() is now a no-op: no automatic sign-in/connect at startup,
so no Zed identity is ever established (this was the real phone-home).
- title_bar: removed the Sign In button + now-unused bindings.
- onboarding: removed the Zed-cloud-AI 'Zed Agent' promo + SignIn action.
The client crate stays compiled but signed-out; collab will be repointed at a
self-hosted server (no Zed auth) later.
C — telemetry neutralized:
- client::telemetry send_event() is a no-op, so all ~43 telemetry::event! call
sites across the tree are inert (one edit, no call-site churn). The Step-1
egress cut in flush_events_inner remains. Nothing is queued, recorded, or sent.
D — crash upload disabled:
- MINIDUMP_ENDPOINT forced to None (ignores build/runtime env), so the upload
paths in reliability.rs are unreachable. Local minidump capture is unaffected.
- RefreshLlmTokenListener is inert (no sign-in event to trigger a Zed cloud token
refresh).
Verified: full cargo build --bin agent-zed = 0 errors. See PRIVACY_HARDENING.md.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
ee39ddeb6c