88a41bedd3
The fork shipped renamed binary/bundle but the product name "Zed" was still
shown everywhere in the UI. Rename the display name to "Joule" (tagline
"Energy-metered agentic coding") while preserving every load-bearing reference.
Display renames (105 .rs files): release_channel display_name, welcome +
onboarding + ai_onboarding, macOS app menu (About/Hide/Quit), window titles,
About panel, settings UI, notifications, update/collab messages, system specs.
Bundle display name (crates/zed/Cargo.toml) -> "Joule" so CFBundleName / the
menu-bar name and the .app are "Joule" (identifier science.transaction.AgentJoule
and the agent-joule binary are unchanged).
Docs (223 .md): product prose Zed -> Joule, fence-aware (code blocks untouched).
Embedded assets (12 JSONC): // comments only.
Legal (4 files): product -> Joule, entity "Zed Industries, Inc." -> "Transaction
Science, Inc.", domain zed.dev -> openie.dev. NOTE: these are structurally Zed's
inherited terms and need a real legal review, not just a rename.
Deliberately PRESERVED (renaming would break the app): font aliases ("Zed Plex
Sans"/".ZedMono" in text_system + assets), HTTP header names (X-Zed-Predict-*),
zed:: action ids, app/bundle identifiers (dev.zed.Zed*, Zed-Editor-* product ids),
zed.dev URLs, ZED_* env vars, crate/package names, "Zed Industries" in non-legal
attribution, and the {zed,Zed} config-dir glob.
Signed + notarized + stapled as Joule.app, installed to /Applications, verified
(Gatekeeper: Notarized Developer ID, FH93XC2VRR). Caveat: test-code string
literals were renamed too, so some `cargo test` assertions may need updating.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
1.1 KiB
| title | description |
|---|---|
| Helix Mode - Joule | Helix-style keybindings and modal editing in Joule. Selection-first editing built on top of Vim mode. |
Helix Mode
Work in progress. Not all Helix keybindings are implemented yet.
Joule's Helix mode is an emulation layer that brings Helix-style keybindings and modal editing to Joule. It builds upon Joule's Vim mode, so much of the core functionality is shared. Enabling helix_mode will also enable vim_mode.
For a guide on Vim-related features that are also available in Helix mode, please refer to our Vim mode documentation.
To check the current status of Helix mode, or to request a missing Helix feature, see the "Are we Helix yet?" discussion.
For a detailed list of Helix's default keybindings, please visit the official Helix documentation.
Core differences
Any text object that works with m i or m a also works with ] and [, so for example ] ( selects the next pair of parentheses after the cursor.