agent-joule/crates/extension_api
Repository files (latest commit first)
Filename Latest commit message Latest commit date
David Charlot ebbc7743e7
Some checks failed
deploy_docs.yml / Upgrade to Rust 1.97 and the latest dependency versions (push) Failing after 0s
extension_bump.yml / Upgrade to Rust 1.97 and the latest dependency versions (push) Failing after 0s
Upgrade to Rust 1.97 and the latest dependency versions
Move the whole workspace to Rust 1.97 (from 1.96) and bump ~120 dependencies to
their latest major versions. The full 230-crate workspace compiles, joule_core's
182 tests pass, the release daemon builds, and LFM2 still loads + runs.

API adaptations for the major bumps:
- rand 0.10: rand_core renamed RngCore->Rng and moved the sugar (random_range,
  from_os_rng) onto RngExt / removed it — updated call sites + imports.
- yawc 0.3: FrameView->Frame with accessor methods; client socket is TcpWebSocket.
- sqlx 0.9 / heed 0.22 / axum 0.8: renamed/removed cargo features.
- core-video 0.6: create_texture_from_image takes &CVImageBuffer; convert via
  TCVImageBuffer::as_image_buffer.
- prost: Message no longer implies Debug — added the bound.
- cargo_toml 1.0: lints is now Inheritable<LintGroups> (Inherited == workspace).
- ed25519-dalek, core-text, core-graphics, cpal: pinned to the versions the
  git-forked deps (open-standands receipts, zed-font-kit, rodio) are built
  against — a split breaks shared SigningKey/CTFont/CGFont/Device types.

Deliberate holds (their own migration, not a blind sweep):
- livekit/libwebrtc/webrtc-sys/coreaudio-rs: the real-time A/V stack, pinned to
  Zed's livekit-rust-sdks fork; latest breaks livekit_client deeply.
- wasmtime 36 + wit-bindgen 0.41: the extension component-model ABI, tied to the
  pinned zed:extension WIT worlds.
- brush-parser 0.3: 0.4 reshapes the AST on the command-safety allow-gate path.
- runtimelib/nbformat/jupyter-protocol 1.x: the REPL Jupyter stack moves majors
  together.

Also: unlisted Zed's hosted-collab SERVER (crates/collab) from the workspace — a
leaf binary nothing depends on, whose pinned sea-orm/sqlx chain blocked the
upgrade; source stays on disk. All open-standards git deps repointed to the forge
URL and bumped to c4b536cf (320fa1e + score_binary).

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-07-17 18:42:09 -04:00
..
src Rebrand: swap the Zed brand mark, zed.dev domain, Zeta model, and zed:// scheme 2026-07-04 20:10:29 -04:00
wit Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
build.rs Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
Cargo.toml Upgrade to Rust 1.97 and the latest dependency versions 2026-07-17 18:42:09 -04:00
LICENSE-APACHE Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
PENDING_CHANGES.md Rebrand Zed -> Joule across UI, docs, embedded assets, and legal 2026-07-03 02:23:35 -04:00
README.md Rebrand Zed -> Joule across UI, docs, embedded assets, and legal 2026-07-03 02:23:35 -04:00

The Joule Rust Extension API

This crate lets you write extensions for Joule 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 <[email protected]>"]
repository = "https://github.com/your/extension-repository"

Cargo metadata

Joule 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 Joule 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 Joule versions

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

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

Joule 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