yenru0/zed

0 Fork 0

Files

T

morgankrey 99739ef047 Restructure AI docs (#57614 )

## Summary

- Restructures the AI docs around quick routing, agent paths, provider
access, and company-specific entry points.
- Moves account-owned AI billing/model pages into Account & Billing
while preserving legacy AI redirects.
- Adds focused pages for Zed Agent, external agents, terminal threads,
agent profiles, skills, instructions, API access, subscriptions,
gateways, and local models.
- Updates related links across Git, authentication, business, migration,
and settings reference docs.

## Validation

- `pnpm dlx prettier@3.5.0 . --write`
- `pnpm dlx prettier@3.5.0 . --check`
- `git diff --check -- docs/src`
- Changed-doc local markdown link sanity check
- `mdbook build docs` was attempted; it is currently blocked by an
unrelated existing `docs/src/vim.md:542` action schema error for
`vim::HelixJumpToWord`.

## Follow-up

- Create a ticket to align Zed's in-app AI configuration surfaces with
this documentation model, including Agent Settings, Configure buttons,
Tools, Profiles, MCP, Skills/Instructions, and plain settings.

## Suggested .rules additions

N/A

Release Notes:

- N/A

2026-06-04 15:55:21 +00:00

2.8 KiB

Raw Blame History

title, description

title	description
Agent Profiles - Zed	Configure Zed Agent profiles for model selection, built-in tool availability, and MCP tool availability.

Agent Profiles

Agent profiles control how the Zed Agent behaves in a thread. A profile can set a default model and choose which built-in tools and MCP tools are available.

Profiles do not decide whether a tool call is allowed automatically. Use Tool Permissions to control allow, deny, and confirm behavior.

Built-in Profiles

Zed includes three built-in profiles:

Write: enables tools for reading, editing, and running commands.
Ask: focuses on read-only codebase questions.
Minimal: uses no project tools.

Configure Profiles

Open the profile selector in the Agent Panel, then click Configure.

You can also run {#action agent::ManageProfiles} from the command palette.

From the profile modal, you can:

create a custom profile
fork an existing profile
configure a profile default model
configure built-in tools
configure MCP tools
delete custom profiles

Profiles and Settings

Profiles are stored under agent.profiles in your settings.

{
  "agent": {
    "profiles": {
      "ask": {
        "name": "Ask",
        "tools": {
          "read_file": true,
          "grep": true,
          "terminal": false,
          "edit_file": false
        },
        "enable_all_context_servers": false,
        "context_servers": {},
        "default_model": {
          "provider": "zed.dev",
          "model": "claude-sonnet-4-5"
        }
      }
    }
  }
}

The exact model IDs and provider IDs depend on your configured LLM Providers.

Profiles vs. Tool Permissions

Setting	Controls	Example
Agent profile	Whether a tool is available in a profile	Disable `terminal` in a read-only profile
Tool permissions	Whether a permission-gated tool call is allowed, denied, or confirmed	Always confirm `terminal` commands

If a tool is not available in the active profile, the Zed Agent cannot use it. If the tool is available and permission-gated, Tool Permissions still controls whether the tool call requires approval.

Agent Path Boundaries

Agent profiles apply to the Zed Agent. External Agents and Terminal Threads do not use Zed Agent profiles unless their integration explicitly supports similar behavior.

2.8 KiB Raw Blame History