entwurf
A thin bridge that lets already-existing agent harnesses address one another by garden id — without pretending to own each other’s transcript, auth, or runtime.
Quick start
npm install -g @junghanacs/entwurf
entwurf setup /path/to/your-project
entwurf check-bridgesetup composes every harness it finds on the host and reports each one PASS / SKIP / FAIL.
How it dispatches
entwurf_v2
Canonical dispatch over an existing garden citizen — control-socket send, meta-mailbox enqueue, or native-push into a live conversation.
entwurf_fresh_call
Opens a NEW sibling session in the operator’s tmux and learns its garden id from the callback it makes.
entwurf_resume_call
Reopens a DORMANT citizen under its own garden id in a visible window, without running a hidden turn.
Five harnesses, one address space
Claude Code
Mailbox-backed self-fetch meta-session, registered by a SessionStart hook.
Copilot CLI
Self-fetch rail with a first-prompt birth hook and an extension-armed receiver.
Antigravity
Native-push citizen with automatic PreInvocation birth and live gRPC delivery.
OMP
Self-fetch citizen opened under the visible-fresh contract.
pi
Adapter that hosts the ACP plugin and the live control-socket surface.
Garden id is deliberate vocabulary
Not a decorative synonym for session id, worker, delegate, or subagent. Each harness keeps its own identity and transcript; entwurf supplies a narrow addressable surface between siblings.