| Filename | Latest commit message | Latest commit date |
|---|---|---|
Complete the rebrand beyond text — the brand mark, domain, model name, and URL
scheme, all of which surface in the UI:
- Logo/icon: replace the Zed "Z" mark in all 13 branded SVGs (ai_zed — the AI
provider icon, zed_agent/two, zed_assistant, zed_logo, zed_x_copilot,
zed_predict*, zed_src_*) with the Joule lightning bolt (bolt_filled), keeping the
filenames + IconName variants so all 67 usages render Joule with no code change.
- Domain: zed.dev -> transaction.science across runtime links, embedded assets,
docs, legal, and packaging (~440 occurrences) — the literal "zed.dev" button,
Help menu, onboarding, and in-context docs links.
- Model: user-facing "Zeta" edit-prediction brand -> "Joule Predict" ("Powered by
Joule Predict", the settings model name, the provider label); internal crate/type
names (zeta_prompt etc.) unchanged.
- URL scheme: zed:// -> joule:// (osx_url_schemes + all deep-link references,
incl. zed-cli:// -> joule-cli://).
Verified: 0 zed.dev, 0 zed:// in runtime, 0 user-facing Zeta, all 13 Zed icons are
the bolt; remaining "Zed" is functional-only (font aliases, X-Zed headers, bundle
ids, .exe paths). Compiles.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
|
||
| .. | ||
| src | ||
| wit | ||
| build.rs | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||
| PENDING_CHANGES.md | ||
| README.md | ||
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-wasip2target installed (rustup target add wasm32-wasip2) - Open the extensions view using the
zed: extensionsaction in the command palette. - Click the
Install Dev Extensionbutton 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 |