diff --git a/docs/src/ai/agent-panel.md b/docs/src/ai/agent-panel.md index 6204cf386cf2afd42a27fe89f75ee0a771b0ba13..7e183d38550d3624a0c9a48051e95ca4c568d72d 100644 --- a/docs/src/ai/agent-panel.md +++ b/docs/src/ai/agent-panel.md @@ -114,14 +114,6 @@ The agent can search your codebase to find relevant context, but providing it ex Add context by typing `@` in the message editor. You can mention files, directories, symbols, previous threads, rules files, and diagnostics. -> **Changed in Preview (v0.225).** See [release notes](/releases#0.225). - -### Images - -You can add images to agent messages on providers that support vision models. OpenAI 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. - -To add an image, use the `/file` slash command and select an image file, or drag an image from your file system directly into the agent panel message editor. You can also copy an image and paste it into the message editor. - When you paste multi-line code selections copied from a buffer, Zed automatically formats them as @-mentions with the file context. To paste content without this automatic formatting, use {#kb agent::PasteRaw} to paste raw text directly. @@ -129,6 +121,14 @@ To paste content without this automatic formatting, use {#kb agent::PasteRaw} to Additionally, 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. +### Images as Context + +It's also possible to attach images in your prompt for providers that support vision models. +OpenAI 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. + +To 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. +Copying an image and pasting it is also supported. + ## Token Usage {#token-usage} Zed surfaces how many tokens you are consuming for your currently active thread near the profile selector in the panel's message editor. @@ -174,8 +174,6 @@ You can explore the exact tools enabled in each profile by clicking on the profi Alternatively, 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. -> **Preview:** This keybinding is available in Zed Preview. It will be included in the next Stable release. - Use {#kb agent::CycleModeSelector} to cycle through available profiles without opening the modal. #### Custom Profiles {#custom-profiles} diff --git a/docs/src/ai/agent-settings.md b/docs/src/ai/agent-settings.md index b351fdfd3b3b15817f05cdf1d1a204d7a91c6eac..0547f19c9ca0e58cb5d63d7ae1c5231d091a6503 100644 --- a/docs/src/ai/agent-settings.md +++ b/docs/src/ai/agent-settings.md @@ -292,20 +292,17 @@ See the [Tool Permissions](./tool-permissions.md) documentation for more example ### Edit Display Mode -> **Changed in Preview (v0.225).** See [release notes](/releases#0.225). - -By default, agent edits open in multi-file review mode. To display agent edits in single-file editors instead, enable `single_file_review`: +Control whether to display review actions (accept & reject) in single buffers after the agent is done performing edits. +The default value is `false`. ```json [settings] { "agent": { - "single_file_review": true + "single_file_review": false } } ``` -When enabled, each file modified by an agent opens in its own editor tab for review. When disabled (default), all changes appear in a unified review interface. - ### Sound Notification Control whether to hear a notification sound when the agent is done generating changes or needs your input. diff --git a/docs/src/ai/llm-providers.md b/docs/src/ai/llm-providers.md index a8aa7a832736f6042e2c5b6d504b77a7e10f5614..8c2dc976fcccfefcf75b4d0dcb71bad353af147f 100644 --- a/docs/src/ai/llm-providers.md +++ b/docs/src/ai/llm-providers.md @@ -174,7 +174,7 @@ Zed enables extended context for supported models (Claude Sonnet 4.5 and Claude > **Preview:** This feature is available in Zed Preview. It will be included in the next Stable release. -Bedrock models that support vision (Claude 3 and later, Amazon Nova Pro and Lite, Meta Llama 3.2 Vision models, Mistral Pixtral) can receive images in conversations and tool results. To send an image, use the slash command `/file` followed by an image path, or drag an image directly into the agent panel. +Bedrock models that support vision (Claude 3 and later, Amazon Nova Pro and Lite, Meta Llama 3.2 Vision models, Mistral Pixtral) can receive images in conversations and tool results. ### Anthropic {#anthropic} diff --git a/docs/src/ai/mcp.md b/docs/src/ai/mcp.md index 482b2e371de71a6c8cab41149ea1759779d5ca25..4797d4b36359be3820a79c96a3cd3cf922d06f8d 100644 --- a/docs/src/ai/mcp.md +++ b/docs/src/ai/mcp.md @@ -86,19 +86,7 @@ Once installation is complete, you can return to the Agent Panel and start promp How reliably MCP tools get called can vary from model to model. Mentioning the MCP server by name can help the model pick tools from that server. -#### Error Handling - -> **Changed in Preview (v0.225).** See [release notes](/releases#0.225). - -When a context server encounters an error while processing a tool call, the agent receives the error message directly and the operation fails. Common error scenarios include: - -- Invalid parameters passed to the tool -- Server-side failures (database connection issues, rate limits) -- Unsupported operations or missing resources - -The error message from the context server will be shown in the agent's response, allowing you to diagnose and correct the issue. Check the context server's logs or documentation for details about specific error codes. - -If you want to _ensure_ a given MCP server will be used, you can create [a custom profile](./agent-panel.md#custom-profiles) where all built-in tools (or the ones that could cause conflicts with the server's tools) are turned off and only the tools coming from the MCP server are turned on. +However, if you want to _ensure_ a given MCP server will be used, you can create [a custom profile](./agent-panel.md#custom-profiles) where all built-in tools (or the ones that could cause conflicts with the server's tools) are turned off and only the tools coming from the MCP server are turned on. As an example, [the Dagger team suggests](https://container-use.com/agent-integrations#zed) doing that with their [Container Use MCP server](https://zed.dev/extensions/mcp-server-container-use): @@ -168,3 +156,15 @@ Note that for [external agents](./external-agents.md) connected through the [Age Regarding the built-in ones, Claude Agent and Codex both support it, and Gemini CLI does not yet. In the meantime, learn how to add MCP server support to Gemini CLI through [their documentation](https://github.com/google-gemini/gemini-cli?tab=readme-ov-file#using-mcp-servers). + +#### Error Handling + +When a MCP server encounters an error while processing a tool call, the agent receives the error message directly and the operation fails. +Common error scenarios include: + +- Invalid parameters passed to the tool +- Server-side failures (database connection issues, rate limits) +- Unsupported operations or missing resources + +The error message from the context server will be shown in the agent's response, allowing you to diagnose and correct the issue. +Check the context server's logs or documentation for details about specific error codes.