Entwurf

entwurf

entwurf connects independent agent harnesses as visible siblings. Open a fresh sibling, or reopen
or message an existing one by its garden id. Every harness keeps its own runtime,
authentication, tools and transcript; Entwurf adds identity, delivery, receipts and named
lifecycle verbs.

Pi ↔ native Claude Code inside the Herdr workbench.
A recorded source-checkout demo: callback → task → native Bash → reply.
Source recipe and original provenance
(the recipe creates a new take; the original private capture is not shipped).

 · maintained by junghanacs.com

Why

- Siblings, not workers. A sibling is a visible session with its own runtime boundary, not a
  disposable worker or a subagent of a new central harness. You and the native harnesses keep
  steering; branches, worktrees, file isolation and internal delegation stay their concern.
- Native harnesses stay native. Claude Code keeps its hooks and tools, Codex its own threads and
  delegation, pi its extensions. Entwurf reconstructs no prompt, hydrates no transcript and mediates
  no credential.
- One address. A garden id names a record-backed citizen. A pane, socket, native session id or
  model is a carrier or an observation, never a second address.
- The same verbs on both screens. In an ordinary tmux session or inside a Herdr workspace, a
  sibling opens and reopens beside you through the same tools. The rail follows where the caller
  runs, with no fallback from one to the other.

Short answers: FAQ.

The four verbs

Every verb returns a receipt, not the sibling's turn result. Capabilities differ by rail, so a
shipped citizen is not a promise of every lifecycle operation; DELIVERY owns each
rail's admission. Antigravity is a legacy citizen: it registers an existing conversation, Entwurf
never launches one,…