Transaction-Science/agent-joule
Watch
1
0
Fork
You've already forked agent-joule
 0
Code Issues Pull requests 2 Projects Releases 7 Packages Wiki Activity Actions
agent-joule/crates/zlog
History
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
David Charlot 88a41bedd3 Rebrand Zed -> Joule across UI, docs, embedded assets, and legal 
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]>
2026-07-03 02:23:35 -04:00
..
src Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
Cargo.toml Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
LICENSE-GPL Baseline: hard fork of zed@e2e7a67 2026-05-30 08:20:23 -04:00
README.md Rebrand Zed -> Joule across UI, docs, embedded assets, and legal 2026-07-03 02:23:35 -04:00

README.md

Zlog

Use the ZED_LOG environment variable to control logging output for Zed applications and libraries. The variable accepts a comma-separated list of directives that specify logging levels for different modules (crates). The general format is for instance:

ZED_LOG=info,project=debug,agent=off
  • Levels can be one of: off/none, error, warn, info, debug, or trace.
  • You don't need to specify the global level, default is trace in the crate and info set by RUST_LOG in Joule.