1---
  2title: AI Coding Agent - Zed Agent Panel
  3description: Use Zed's AI coding agent to generate, refactor, and debug code with tool calling, checkpoints, and multi-model support.
  4---
  5
  6# Agent Panel
  7
  8The Agent Panel is where you interact with AI agents that can read, write, and run code in your project.
  9It's the core of Zed's AI code editing experience — use it for code generation, refactoring, debugging, documentation, and general questions.
 10
 11Open it with `agent: new thread` from [the Command Palette](../getting-started.md#command-palette) or click the ✨ icon in the status bar.
 12
 13## Getting Started {#getting-started}
 14
 15If you're using the Agent Panel for the first time, you need to have at least one LLM provider or external agent configured.
 16You can do that by:
 17
 181. [subscribing to our Pro plan](https://zed.dev/pricing), so you have access to our hosted models
 192. [using your own API keys](./llm-providers.md#use-your-own-keys), either from model providers like Anthropic or model gateways like OpenRouter.
 203. using an [external agent](./external-agents.md) like [Gemini CLI](./external-agents.md#gemini-cli) or [Claude Agent](./external-agents.md#claude-agent)
 21
 22## Overview {#overview}
 23
 24With an LLM provider or external agent configured, type in the message editor and press `enter` to submit.
 25Expand the editor with {#kb agent::ExpandMessageEditor} if you need more room.
 26
 27Responses stream in with indicators showing [which tools](./tools.md) the model is using.
 28The sections below cover what you can do from here.
 29
 30> Note that for external agents, like [Gemini CLI](./external-agents.md#gemini-cli) or [Claude Agent](./external-agents.md#claude-agent), some of the features outlined below may _not_ be supported—for example, _restoring threads from history_, _checkpoints_, _token usage display_, and others.
 31> Their availability varies depending on the agent.
 32
 33### Creating New Threads {#new-thread}
 34
 35By default, the Agent Panel uses Zed's first-party agent.
 36
 37To choose another agent, go to the plus button in the top-right of the Agent Panel and pick either one of the [external agents](./external-agents.md) installed out of the box or a new [Text Thread](./text-threads.md).
 38
 39### Editing Messages {#editing-messages}
 40
 41Any message that you send to the model is editable.
 42You can click on the card that contains your message and re-submit it with an adjusted prompt and/or new pieces of context.
 43
 44### Queueing Messages
 45
 46Messages sent while the agent is in the generating state get, by default, queued.
 47
 48For the Zed agent, queued messages get sent at the next turn boundary, which is usually between a tool call and a response, whereas for external agents, the message gets sent at the end of the generation.
 49
 50You can edit or remove (an individual or all) queued messages.
 51You can also still interrupt the agent immediately if you want by either clicking on the stop button or by clicking the "Send Now" (double-enter) on a queued message.
 52
 53### Checkpoints {#checkpoints}
 54
 55Every time the model performs an edit, you should see a "Restore Checkpoint" button at the top of your message, allowing you to return your code base to the state it was in prior to that message.
 56
 57The checkpoint button appears even if you interrupt the thread midway through an edit, as this is likely a moment when you've identified that the agent is not heading in the right direction and you want to revert back.
 58
 59### Context Menu {#context-menu}
 60
 61Right-click on any agent response in the thread view to access a context menu with the following actions:
 62
 63- **Copy Selection**: Copies the currently selected text as Markdown (available when text is selected).
 64- **Copy This Agent Response**: Copies the full text of the agent response you right-clicked on.
 65- **Scroll to Top / Scroll to Bottom**: Scrolls to the beginning or end of the thread, depending on your current position.
 66- **Open Thread as Markdown**: Opens the entire thread as a Markdown file in a new tab.
 67
 68### Navigating the Thread {#navigating-the-thread}
 69
 70In long conversations, use the scroll arrow buttons at the bottom of the panel to jump to your most recent prompt or to the very beginning of the thread.
 71
 72### Navigating History {#navigating-history}
 73
 74To quickly navigate through recently updated threads, use the {#kb agent::ToggleNavigationMenu} binding when focused on the panel's editor, or click the menu icon button at the top right of the panel.
 75Doing that will open a dropdown that shows you your six most recently updated threads.
 76
 77To view all historical conversations, reach for the `View All` option from within the same menu or via the {#kb agent::OpenHistory} binding.
 78
 79Thread titles are auto-generated based on the content of the conversation.
 80But you can also edit them manually by clicking the title and typing, or regenerate them by clicking the "Regenerate Thread Title" button in the ellipsis menu in the top right of the panel.
 81
 82### Following the Agent {#following-the-agent}
 83
 84Follow the agent as it reads and edits files by clicking the crosshair icon at the bottom left of the panel.
 85Your editor will jump to each file the agent touches.
 86
 87You can also hold `cmd`/`ctrl` when submitting a message to automatically follow.
 88
 89### Get Notified {#get-notified}
 90
 91If you send a prompt to the Agent and then put Zed in the background, you can choose to be notified when its generation wraps up via:
 92
 93- a visual notification that appears in the top right of your screen
 94- a sound notification
 95
 96These notifications can be used together or individually, and you can use the `agent.notify_when_agent_waiting` and `agent.play_sound_when_agent_done` settings keys to customize that, including turning both off entirely.
 97
 98### Reviewing Changes {#reviewing-changes}
 99
100Once the agent has made changes to your project, the panel will surface which files, how many of them, and how many lines have been edited.
101
102To see which files specifically have been edited, expand the accordion bar that shows up right above the message editor or click the `Review Changes` button ({#kb agent::OpenAgentDiff}), which opens a special multi-buffer tab with all changes.
103
104You can accept or reject each individual change hunk, or the whole set of changes made by the agent.
105
106Edit diffs also appear in singleton buffers.
107If your active tab had edits made by the AI, you'll see diffs with the same accept/reject controls as in the multi-buffer.
108You can turn this off, though, through the `agent.single_file_review` setting.
109
110## Adding Context {#adding-context}
111
112The agent can search your codebase to find relevant context, but providing it explicitly improves response quality and reduces latency.
113
114Add context by typing `@` in the message editor.
115You can mention files, directories, symbols, previous threads, rules files, and diagnostics.
116
117When you paste multi-line code selections copied from a buffer, Zed automatically formats them as @-mentions with the file context.
118To paste content without this automatic formatting, use {#kb agent::PasteRaw} to paste raw text directly.
119
120### Selection as Context
121
122Additionally, you can also select text in a buffer or terminal and add it as context by using the {#kb agent::AddSelectionToThread} keybinding, running the {#action agent::AddSelectionToThread} action, or choosing the "Selection" item in the `+` menu in the message editor.
123
124### Images as Context
125
126It's also possible to attach images in your prompt for providers that support vision models.
127OpenAI GPT-4o and later, Anthropic Claude 3 and later, Google Gemini 1.5 and 2.0, and Bedrock vision models (Claude 3+, Amazon Nova Pro and Lite, Meta Llama 3.2 Vision, Mistral Pixtral) all support image inputs.
128
129To add an image, you can either search in your project's directory by @-mentioning it, or drag it from your file system directly into the agent panel message editor.
130Copying an image and pasting it is also supported.
131
132## Token Usage {#token-usage}
133
134Zed surfaces how many tokens you are consuming for your currently active thread near the profile selector in the panel's message editor.
135
136Once you approach the model's context window, a banner appears above the message editor suggesting to start a new thread with the current one summarized and added as context.
137You can also do this at any time with an ongoing thread via the "Agent Options" menu on the top right, where you'll see a "New from Summary" button, as well as simply @-mentioning a past thread in a new one..
138
139## Changing Models {#changing-models}
140
141After you've configured your LLM providers—either via [a custom API key](./llm-providers.md) or through [Zed's hosted models](./models.md)—you can switch between their models by clicking on the model selector on the message editor or by using the {#kb agent::ToggleModelSelector} keybinding.
142
143> The same model can be offered via multiple providers - for example, Claude Sonnet 4.5 is available via Zed Pro, OpenRouter, Anthropic directly, and more.
144> Make sure you've selected the correct model **_provider_** for the model you'd like to use, delineated by the logo to the left of the model in the model selector.
145
146### Favoriting Models
147
148You can mark specific models as favorites either through the model selector, by clicking on the star icon button that appears as you hover the model, or through your settings via the `agent.favorite_models` settings key.
149
150Cycle through your favorites with {#kb agent::CycleFavoriteModels} without opening the model selector.
151
152## Using Tools {#using-tools}
153
154The Agent Panel supports tool calling, which enables agentic editing.
155Zed includes several [built-in tools](./tools.md) for searching your codebase, editing files, running terminal commands, and more.
156
157You can also extend the set of available tools via [MCP Servers](./mcp.md).
158
159### Profiles {#profiles}
160
161Profiles act as a way to group tools.
162Zed offers three built-in profiles and you can create as many custom ones as you want.
163
164#### Built-in Profiles {#built-in-profiles}
165
166- `Write`: A profile with tools to allow the LLM to write to your files and run terminal commands.
167  This one essentially has all built-in tools turned on.
168- `Ask`: A profile with read-only tools.
169  Best for asking questions about your code base without the concern of the agent making changes.
170- `Minimal`: A profile with no tools.
171  Best for general conversations with the LLM where no knowledge of your code base is necessary.
172
173You can explore the exact tools enabled in each profile by clicking on the profile selector button > `Configure` button > the one you want to check out.
174
175Alternatively, you can also use either the command palette, by running {#action agent::ManageProfiles}, or the keybinding directly, {#kb agent::ManageProfiles}, to have access to the profile management modal.
176
177Use {#kb agent::CycleModeSelector} to cycle through available profiles without opening the modal.
178
179#### Custom Profiles {#custom-profiles}
180
181You can also create a custom profile through the Agent Profile modal.
182From there, you can choose to `Add New Profile` or fork an existing one with a custom name and your preferred set of tools.
183
184It's also possible to override built-in profiles.
185In the Agent Profile modal, select a built-in profile, navigate to `Configure Tools`, and rearrange the tools you'd like to keep or remove.
186
187Zed will store this profile in your settings using the same profile name as the default you overrode.
188
189All custom profiles can be edited via the UI or by hand under the `agent.profiles` key in your settings file.
190
191To delete a custom profile, open the Agent Profile modal, select the profile you want to remove, and click the delete button.
192
193### Tool Permissions
194
195> **Note:** In Zed v0.224.0 and above, tool approval is controlled by `agent.tool_permissions.default`.
196> In earlier versions, it was controlled by the `agent.always_allow_tool_actions` boolean (default `false`).
197
198Zed's Agent Panel provides the `agent.tool_permissions.default` setting to control tool approval behavior:
199
200- `"confirm"` (default) — Prompts for approval before running any tool action
201- `"allow"` — Auto-approves tool actions without prompting
202- `"deny"` — Blocks all tool actions
203
204When the agent requests permission for an action, the confirmation menu includes options to allow or deny once, plus "Always for <tool>" choices that set a tool-level default.
205When Zed can extract a safe pattern from the input, it also offers pattern-based "Always for ..." choices that add `always_allow`/`always_deny` rules.
206MCP tools only support tool-level defaults.
207
208Even with `"default": "allow"`, per-tool `always_deny` and `always_confirm` patterns are still respected — so you can auto-approve most actions while blocking or gating specific ones.
209
210Learn more about [how tool permissions work](./tool-permissions.md), how to further customize them, and other details.
211
212### Model Support {#model-support}
213
214Tool calling needs to be individually supported by each model and model provider.
215Therefore, despite the presence of built-in tools, some models may not have the ability to pick them up.
216You should see a "No tools" label if you select a model that falls into this case.
217
218All [Zed's hosted models](./models.md) support tool calling out-of-the-box.
219
220### MCP Servers {#mcp-servers}
221
222Similarly to the built-in tools, some models may not support all tools included in a given MCP Server.
223Zed's UI will inform you about this via a warning icon that appears close to the model selector.
224
225## Text Threads {#text-threads}
226
227["Text Threads"](./text-threads.md) present your conversation with the LLM in a different format—as raw text.
228With text threads, you have full control over the conversation data.
229You can remove and edit responses from the LLM, swap roles, and include more context earlier in the conversation.
230
231Text threads are Zed's original assistant panel format, preserved for users who want direct control over conversation data.
232Autonomous code editing (where the agent writes to files) is only available in the default thread format, not text threads.
233
234## Errors and Debugging {#errors-and-debugging}
235
236If you hit an error or unusual LLM behavior, open the thread as Markdown with `agent: open thread as markdown` and attach it to your GitHub issue.
237
238You can also open threads as Markdown by clicking on the file icon button, to the right of the thumbs down button, when focused on the panel's editor.
239
240## Feedback {#feedback}
241
242You can rate agent responses to help improve Zed's system prompt and tools.
243
244> Note that rating responses will send your data related to that response to Zed's servers.
245> See [AI Improvement](./ai-improvement.md) and [Privacy and Security](./privacy-and-security.md) for more information about Zed's approach to AI improvement, privacy, and security.
246> **_If you don't want data persisted on Zed's servers, don't rate_**.
247> We will not collect data for improving our Agentic offering without you explicitly rating responses.
248
249To help improve Zed's system prompt and tools, rate responses with the thumbs up/down controls at the end of each response.
250In case of a thumbs down, a new text area will show up where you can add more specifics about what happened.
251
252You can provide feedback on the thread at any point after the agent responds, and multiple times within the same thread.