9ad521e801
## Documentation Update Summary ### Changes Made | File | Change | Related Code | | --- | --- | --- | | `docs/src/ai/edit-prediction.md` | Updated Codestral setup instructions to use Settings Editor path instead of outdated `agent::OpenSettings` action reference | Settings Editor provider configuration flow | ### Rationale The primary documentation update addresses outdated instructions in the Codestral setup section. The original text referenced an `agent::OpenSettings` action that directed users to an "Agent Panel settings view" which no longer reflects the current UI flow. The updated instructions now guide users through the Settings Editor with platform-specific keyboard shortcuts and provide an alternative status bar path. ### Review Notes - **Codestral instructions**: Reviewers should verify the Settings Editor navigation path (`Cmd+,` → search "Edit Predictions" → **Configure Providers**) matches the current Zed UI - **Status bar alternative**: The alternative path via "edit prediction icon in the status bar" should be confirmed as accurate --- ## Update from 2025-12-21 20:25 --- **Source**: [#44914](https://github.com/zed-industries/zed/pull/44914) - settings_ui: Add Edit keybindings button **Author**: @probably-neb Now I have all the context needed to create a comprehensive documentation update summary. ## Documentation Update Summary ### Changes Made | File | Change | Related Code | | --- | --- | --- | | docs/src/ai/agent-panel.md | Added documentation for `agent::PasteRaw` action, explaining automatic @mention formatting for pasted code and how to bypass it | PR #45254 | ### Rationale PR #45254 ("agent_ui: Improve UX when pasting code into message editor") introduced the `agent::PasteRaw` action, which allows users to paste clipboard content without automatic formatting. When users copy multi-line code from an editor buffer and paste it into the Agent panel, Zed now automatically formats it as an @mention with file context. The `PasteRaw` action provides a way to bypass this behavior when raw text is preferred. This documentation update ensures users can discover both: 1. The new automatic @mention formatting behavior 2. The keybinding to bypass it when needed ### Review Notes - The new paragraph was placed in the "Adding Context" section, immediately after the existing note about image pasting support—this maintains logical flow since both relate to pasting behavior - Uses the standard `{#kb agent::PasteRaw}` syntax for keybinding references, consistent with other keybinding documentation in the file - The documentation passed Prettier formatting validation without modifications --- ### Condensed Version (for commit message) ``` docs(agent-panel): Document PasteRaw action for bypassing auto @mention formatting Added explanation that multi-line code pasted from editor buffers is automatically formatted as @mentions, with keybinding to paste raw text. Related: PR #45254 ``` Release Notes: - N/A --------- Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> Co-authored-by: Zed Zippy <234243425+zed-zippy[bot]@users.noreply.github.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.