Workflow

The daily loop you know. The guarantees you've never had.

heddle init in an existing Git repo. Capture as you work. Spawn task-threads when the work splits. Undo what didn't land. Bridge back to Git when you're ready. Nothing you depend on disappears.

01

Adopt

Drop into your existing Git repo.

One command. No migration. Git stays your bridge to branches, PRs, and reviewers. Heddle records agent work as task-threads underneath.

bash$ cd your-repo$ heddle initinitialized · git-overlay mode · adopted main$ heddle statuson thread main · clean · 0 captures since adoption
02

Work

Start a task-thread. Capture as you go.

Each task gets its own named thread, isolated by default. Captures replace the staging dance: intent, agent, confidence, optional signature — all carried as structural data, not parsed from a commit message later.

task/biscuit-authz

$ heddle start task/biscuit-authz --task "replace JWT with Biscuit capabilities"
thread started: task/biscuit-authz
  parent: main @ hd-f1a23b8c
$ heddle capture -m "scaffold biscuit verifier"
state      hd-7c2e84f1
agent      claude-opus-4.7 · 0.94 confidence
  · 9 captures · 3 retries · 1 abort recorded so far
03

Review

Read the task as one object.

Semantic compare shows the structural change, not raw line diffs. The thread surface composes captures, retries, abandoned forks, and tests into one record you can scan in seconds.

heddle compare · semantic

$ heddle compare task/biscuit-authz main --semantic
+ src/server/auth/biscuit.rs    2 new symbols · 1 rewrite
~ src/proto/auth.proto          JwtClaims removed · AuthRequest renamed
+ tests/auth/biscuit_spec.rs    12 new tests
$ heddle thread show task/biscuit-authz
  16 events · 9 captures · 3 retries · 1 abort · 1 conflict · 1 test · 1 merge
status: reviewable · signed: ed25519:a8f3…c1d7 ✓
04

Bridge to Git

Hand the task back to Git.

When the task is reviewable, export it as a single Git commit on the branch your team already reviews. Round-trip verified — original commits unchanged. Your reviewers, your CI, your PR template stay exactly as they are.

heddle bridge git export

$ heddle bridge git export task/biscuit-authz
exported 1 task · 1 commit on feature/biscuit-authz
  round-trip verified · original Git history unchanged
$ git push origin feature/biscuit-authz
  task summary printable via `heddle review show`

Terminal-native

Heddle state is structured data. Not parsed text.

Every command supports --json. Shell completions for bash, zsh, and fish — one step to install. Automation reads Heddle the way it reads a database, not the way it parses stdout.