- Rust 94.7%
- JSON-with-Comments 2.9%
- Inno Setup 0.5%
- Python 0.4%
- Tree-sitter Query 0.4%
- Other 0.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
2f90bb4c2e
SOTA multi-agent coding (AOrchestra, +16pp pass@1 on SWE-Verified/GAIA/Terminal-Bench) auto-GENERATES specialized sub-agents from a task rather than hand-writing them, runs them by dependency, and synthesizes. agent-joule had the execution substrate (worktree sessions, attenuable grants, fanout) but not the specialization + scheduling layer. This adds it, deterministic-first and sovereign. - joule_core::subagents: SubagentSpec (role + focus + tools + depends_on) and parse_plan, which VALIDATES a model-proposed decomposition — bounded (MAX_SUBAGENTS), unique ids, no dangling dependency, no cycle — so nothing downstream runs a malformed plan. execution_waves topologically schedules the plan into parallel waves (Kahn's algorithm, cycle-detecting, deterministic). synthesis_context frames the final merge; decomposition_prompt is the deterministic decomposition ask. The model only proposes; scheduling, capability attenuation, and synthesis framing are deterministic. - joule_coded: an `orchestrate` control method decomposes a task, runs each sub-agent in wave order as a metered run_loop_metered pass with its focused intent (each's energy captured), synthesizes, and seals an OrchestrationReport (plan + per-sub-agent results + energy) for `orchestration`. So a multi-agent run reports the joules the whole fleet of sub-agents spent — energy-metered orchestration no one else measures. Verified: 7 subagents unit tests (parse+schedule, parallel waves, cycle/dangling/dup/ empty/oversize rejection, synthesis); lean + l3 daemon builds; the control methods validate + model-gate correctly. |
||
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| dev-docs | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| JOULE_CODE.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| PRIVACY_HARDENING.md | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| SIGNING.md | ||
| typos.toml | ||
agent-joule — Joule Code reference consumer
agent-joule is the reference editor for Joule Code, the Transaction Science open standard for energy-attributed, federated, no-phone-home agentic coding. It is a hard fork of the Zed editor, stripped of its cloud ties and rebuilt around the Joule Code commitments: drive vendors' own logged-in coding agents over ACP, meter every turn in joules, and never phone home.
It is not a paid coding tool with a token markup. The protocol is owned by no one; agent-joule is one (SOTA) implementation of it.
What it does
- Federates frontier coding agents. Connect Claude Code, Gemini, or Codex from one panel. agent-joule launches the vendor's own logged-in CLI over the Agent Client Protocol (ACP) — the vendor's client owns its credential; agent-joule never sees or transports a token. These agents are the Joule Code cascade's L4 (Wire) tier.
- Meters energy. Every session surfaces a real
joule-code-receipt::Receipt:⚡ N J this session (est.) · L4. The number is computed from the agent's actual reported token usage; theest.is honest — it is anEstimatorreading because no hardware energy interface is in the path yet (Joule Code SPEC §6). When a metered backend is present, the same surface shows ameasuredfigure. - Does not phone home. Sign-in, telemetry, crash upload, and auto-update are removed; a build-level egress backstop makes Joule-host URLs unreachable; the ACP-registry auto-fetch is off. Startup is network-silent — verified by packet capture. See
PRIVACY_HARDENING.md.
Joule Code conformance
agent-joule implements the Joule Code v0.1 commitments it is positioned to carry — the no-capture posture (verified) and a live receipt surface — and binds the federation legs as the cascade's L4 tier. The full clause-by-clause map (what is implemented, partial, and pending) is in JOULE_CODE.md. The standard's lean reference library (joule-code-rs) and conformance suite live in the open-standards repository; agent-joule consumes it as a dependency rather than vendoring a copy.
Build and run
cargo build --bin agent-joule
./target/debug/agent-joule
Open the federation panel with ctrl-cmd-a. Connecting an agent requires that vendor's CLI to be installed and logged in (e.g. claude, gemini); registry agents are fetched via npx on first connect. A local OpenAI-compatible model (e.g. vLLM at localhost:8000) is registered as a direct provider — the cascade's L3 (local model) tier.
For building on each platform, the upstream Joule development guides still apply: macOS, Linux, Windows.
Licence
agent-joule inherits Joule's GPL-3.0-or-later licence (LICENSE-GPL; portions Apache-2.0, LICENSE-APACHE). The Joule Code standard it consumes is separately and permissively licensed (Apache-2.0 reference code, CC-BY-4.0 spec text); a GPL reference editor consuming a permissive standard is intentional.
License information for third-party dependencies must be correctly provided for CI to pass; agent-joule retains Joule's cargo-about setup under script/licenses/.
Upstream
agent-joule is a hard fork of zed-industries/zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter, developed by Zed Industries, Inc. All credit for the editor foundation is theirs. agent-joule diverges in one direction: removing the cloud dependencies and building the Joule Code substrate in their place. Upstream documentation, contribution guidance, and community links live at zed.dev and the upstream repository.