In this guide
  1. Test editing before AI features
  2. Distinguish models and agents
  3. Understand Personal access
  4. Inspect data handling by feature
  5. Example: hand off a contained edit
  6. Separate disabling AI and ending billing

Test editing before AI features

Test language diagnostics, tests, debugging and Git inspection before judging AI output. Inventory required extensions and project settings when moving from another editor. An attractive model response cannot compensate for losing necessary everyday operations. Pilot one project so migration effort remains visible and reversible.

Distinguish models and agents

Zed can use model access for its own agent or run an external agent through a separate integration. External agents own their authentication and provider relationship. Changing Zed’s model configuration does not necessarily change that external arrangement. Record the authority for authentication and billing so failures can be diagnosed at the right boundary.

Understand Personal access

Personal is a free editor, not payment for independently configured providers or agents. Distinguish Zed-hosted inference from your own provider arrangement. The client being free does not imply unlimited included model use. Inspect the route actually used for a task before attributing a cost or allowance to the editor.

Inspect data handling by feature

Chat, edit prediction and external agents need not share one data boundary. A local model choice also does not establish the configuration of every other feature. Inspect the effective settings and provider terms before private code is introduced; a general privacy description is not a guarantee covering every independently connected component.

Example: hand off a contained edit

For a hypothetical pilot, add one optional form field, verify behavior and preserve the diff in Git. Ask another developer to review and continue it. If work depends on private knowledge of the first operator’s settings, document the non-secret shared requirements. Continuation is useful adoption evidence beyond the first completed screen.

Separate disabling AI and ending billing

You can keep the editor while disabling AI, but disabling a feature is not cancellation of every subscription. Check independent provider and external-agent arrangements separately. Preserve code and non-secret configuration, then verify billing and access changes before considering an operating switch complete.

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure