Agents
Every agent runs on its own thread. Every state carries its author. The reasoning survives the session so the next agent picks up where the last one left off.
heddle agent ls — heddle/core-services
feature/auth-middleware writing tests for scope denialchore/structured-logging refactoring log handlerfix/migration-0042 awaiting signaturedocs/agents-api-reference waiting for review feedbackIsolated worktrees
Each worktree is a lightweight pointer into the shared object store. Any agent gets an independent working directory backed by the full history. Isolation is structural — not coordinated, not negotiated.
heddle start feature/auth --agent claude-opus-4.7 Attribution
The agent registry records ID, provider, model, and status at spawn time. That metadata is structural — threaded into the object model from the first write. When work is merged, attribution from every agent is preserved.
You always know what each agent did, under which model, with what authorization. The record survives the merge.
lm-a8f3c1d7ed25519:a8f3…c1d7 ✓Multi-agent coordination
Each agent works on its own worktree with independent state. Snapshot isolation is structural — the worktree holds its own view, the shared object store keeps the record consistent.
Merge when the work is ready. Attribution from every agent is preserved through the merge. You always know who contributed which state.
Context annotations
Constraints, invariants, and design rationale attach directly to the code they govern — scoped to a file, a symbol, or a line range. When the next agent opens the same function, the annotation is already there.
src/auth/enforce.rs fn authorize(token: &Token) lines 34–42Empty token scope must return `Deny::NoScope`. Never fall through to the role check — role resolution assumes a non-empty scope and will panic on the first index access.
src/store/state.rs struct State moduleThe state DAG is append-only. A state's id (BLAKE3 content hash) is immutable once written. Rebase and collapse create new states; originals are never mutated and remain reachable from their original refs.
src/refs/threads.rs fn resolve_thread(name) lines 118–147Thread resolution walks the DAG upward to the most recent common ancestor rather than the named head. Agents that forked earlier keep a stable view even after the parent rebases — no silent drift during long-running sessions.
Foundations for annotations ship today in the object model; the editing surfaces are on the roadmap. Clearly labeled throughout.
A codebase that remembers
Constraints and rationale live beside the code they govern — not in a wiki that falls behind, not in a channel that scrolls away. Scoped to the file, the symbol, or the line. Carried forward on every snapshot. When something is about to change, the context is already there.