zed/crates/extension_api
Shuhei Kadowaki 9663d059bc
extension_api: Add language server schema methods (#48334)
(This should be merged after #48332)

This PR exposes the LSP settings schema functionality to extensions,
allowing them to provide JSON schema for `initialization_options` and
`settings` fields to enable autocomplete in settings files.

New extension API methods (v0.8.0+):
- `language_server_initialization_options_schema`
- `language_server_settings_schema`

Both methods return an optional JSON string conforming to JSON schema.
Older extension versions gracefully return `None`.

Release Notes:

- Added support for settings schemas for the next version of the
extension API so that settings autocompletion can be provided for
language server settings.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: MrSubidubi <finn@zed.dev>
2026-03-07 11:05:10 +01:00
..
src extension_api: Add language server schema methods (#48334) 2026-03-07 11:05:10 +01:00
wit extension_api: Add language server schema methods (#48334) 2026-03-07 11:05:10 +01:00
build.rs chore: Fix several style lints (#17488) 2024-09-06 11:58:39 +02:00
Cargo.toml zed_extension_api: Fork new version of extension API (#44025) 2025-12-02 22:26:40 +00:00
LICENSE-APACHE Add initial support for defining language server adapters in WebAssembly-based extensions (#8645) 2024-03-01 16:00:55 -08:00
PENDING_CHANGES.md zed_extension_api: Start a list of pending changes (#16305) 2024-08-15 13:10:46 -04:00
README.md zed_extension_api: Release v0.6.0 (#32945) 2025-06-18 14:05:29 +00:00

The Zed Rust Extension API

This crate lets you write extensions for Zed in Rust.

Extension Manifest

You'll need an extension.toml file at the root of your extension directory, with the following structure:

id = "my-extension"
name = "My Extension"
description = "..."
version = "0.0.1"
schema_version = 1
authors = ["Your Name <you@example.com>"]
repository = "https://github.com/your/extension-repository"

Cargo metadata

Zed extensions are packaged as WebAssembly files. In your Cargo.toml, you'll need to set your crate-type accordingly:

[dependencies]
zed_extension_api = "0.6.0"

[lib]
crate-type = ["cdylib"]

Implementing an Extension

To define your extension, create a type that implements the Extension trait, and register it.

use zed_extension_api as zed;

struct MyExtension {
    // ... state
}

impl zed::Extension for MyExtension {
    // ...
}

zed::register_extension!(MyExtension);

Testing your extension

To run your extension in Zed as you're developing it:

  • Make sure you have Rust installed
  • Have the wasm32-wasip2 target installed (rustup target add wasm32-wasip2)
  • Open the extensions view using the zed: extensions action in the command palette.
  • Click the Install Dev Extension button in the top right
  • Choose the path to your extension directory.

Compatible Zed versions

Extensions created using newer versions of the Zed extension API won't be compatible with older versions of Zed.

Here is the compatibility of the zed_extension_api with versions of Zed:

Zed version zed_extension_api version
0.192.x 0.0.1 - 0.6.0
0.186.x 0.0.1 - 0.5.0
0.184.x 0.0.1 - 0.4.0
0.178.x 0.0.1 - 0.3.0
0.162.x 0.0.1 - 0.2.0
0.149.x 0.0.1 - 0.1.0
0.131.x 0.0.1 - 0.0.6
0.130.x 0.0.1 - 0.0.5
0.129.x 0.0.1 - 0.0.4
0.128.x 0.0.1