Answer: To develop a Zed extension locally, install it as a dev extension by clicking the `Install Dev Extension` button on the extensions page (or the `zed: install dev extension` action) and selecting the directory containing your extension. You should first install Rust via rustup, and extensions that provide grammars additionally require the wasi-sdk. Status: Overdue (check was due 2026-11-20T13:40:34Z and has not succeeded) Entry: tool/zed/install-and-setup/develop-extension-locally Revision: 1 Digest: sha256:f0715e950656cb49 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:02:08Z Last changed: 2026-11-13T04:02:08Z Last verified: 2026-11-19T13:40:34Z Next check: 2026-11-20T13:40:34Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Install method | Install Dev Extension | [1] | 2026-11-19 Rust target | wasm32-wasip2 | [1] | 2026-11-19 Prerequisite | install Rust via rustup | [1] | 2026-11-19 Grammar requirement | wasi-sdk | [1] | 2026-11-19 Environment variable | WASI_SDK_PATH | [1] | 2026-11-19 Debug command | zed --foreground | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/extensions/developing-extensions.md". https://zed.dev/docs/extensions/developing-extensions.md Role: primary. Accessed: 2026-11-19T13:40:34Z Quote: "click the `Install Dev Extension` button (or the zed: install dev extension action) and select the directory containing your extension." (Supports: Install method) Quote: "Zed uses the `wasm32-wasip2` Rust target to compile extensions." (Supports: Rust target) Quote: "Before starting to develop an extension for Zed, be sure to [install Rust via rustup](https://www.rust-lang.org/tools/install)." (Supports: Prerequisite) Quote: "Extensions that provide grammars additionally require the [wasi-sdk](https://github.com/WebAssembly/wasi-sdk) to compile Tree-sitter parsers." (Supports: Grammar requirement) Quote: "you can point Zed at an existing installation by setting the `WASI_SDK_PATH` environment variable to its root directory" (Supports: Environment variable) Quote: "close and relaunch Zed from the command line with `zed --foreground`, which shows more verbose INFO-level logs." (Supports: Debug command) Snapshot SHA-256: b73ea3ccd7a4fdc3fa2f728f287afba35cd6394c29e3c303441a722cb228b620 (captured 2026-11-13T04:02:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:02:08Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:40:34Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:40:34Z Last attempt: 2026-11-19T13:40:34Z Notes and limitations: Extracted automatically from a single official source (section "Developing an Extension Locally"). Human-readable page: https://zed.dev/docs/extensions/developing-extensions.html Related: https://latestn.com/tool/zed/install-and-setup/elm-setup How do I set up Elm support in Zed? https://latestn.com/tool/zed/install-and-setup/enable-clojure-support How do I enable Clojure support in Zed? https://latestn.com/tool/zed/install-and-setup/enable-groovy-support How do I enable Groovy language support in Zed? https://latestn.com/tool/zed/install-and-setup/business-getting-started How do I get started with Zed Business for my team? https://latestn.com/tool/zed/install-and-setup/dart-prerequisites What do I need to install to use Dart in Zed? https://latestn.com/tool/zed/install-and-setup/dev-containers-requirements What are the requirements to use Dev Containers in Zed? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:02:08Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/install-and-setup/develop-extension-locally/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/install-and-setup/develop-extension-locally POST: https://latestn.com/dispute/tool/zed/install-and-setup/develop-extension-locally with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/install-and-setup/develop-extension-locally?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I develop a Zed extension locally? Revision 1, last verified 2026-11-19T13:40:34Z. https://latestn.com/tool/zed/install-and-setup/develop-extension-locally (accessed 2026-11-21T10:00:51Z). @misc{LatestN_tool_zed_install_and_setup_develop_extension_locally_r1, title = {How do I develop a Zed extension locally?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/install-and-setup/develop-extension-locally}}, note = {Revision 1; digest sha256:f0715e950656cb49; last verified 2026-11-19T13:40:34Z; accessed 2026-11-21T10:00:51Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/install-and-setup/develop-extension-locally