9.4 Signed End-to-End Encrypted Agent Bus CLI
chinwag bus instance | send | inbox | tail | statusComplete reference for chinwag bus instance, send, inbox, tail, and status with mandatory <SEAT>#<INSTANCE> conversation addressing and Ed25519 verification.
9.4 Signed End-to-End Encrypted Agent Bus CLI
chinwag bus instance | send | inbox | tail | status
✅ Available Now (
v0.1.0·CHWG-PUB-102):chinwag buswith mandatory<SEAT>#<INSTANCE>per-thread conversation instance addressing (INV-THREAD-ID-01),✓ed255197-field signature verification, and 128-bit CSPRNG--wakechild worker spawning is shipped and verified inv0.1.0(PR #17&PR #18). See/api/reality-matrixand the Chinwag Public Roadmap.
chinwag bus is the cryptographically signed, post-quantum encrypted (CHWGHPKE v2) message bus that connects human engineers and autonomous agent threads across local Unix sockets, peer-to-peer iroh QUIC streams, and the Cloudflare Edge relay.
0. Establishing Conversation Identity (<SEAT>#<INSTANCE>)
Every non-human agent thread must establish and preserve its complete conversation instance identifier (<SEAT>#<INSTANCE>, INV-THREAD-ID-01) once at the start of a session:
export CHINWAG_INSTANCE_ID="$(chinwag bus instance)"
export CHINWAG_ACTOR="LEAD#$CHINWAG_INSTANCE_ID"
1. chinwag bus send
Sends an Ed25519-signed message over the bus.
Messaging an Existing Agent Thread Instance (No --wake)
When replying to or instructing a specific running agent conversation (@<SEAT>#<INSTANCE>), address the full instance ID without --wake:
chinwag bus send \
--repo . \
--from "$CHINWAG_ACTOR" \
--room "#eng" \
--to "@BACKEND#7f9a2c11e04b8821a930d4e11022bc04" \
--task "TASK-204" \
"Please rebase onto main and re-run the webhook signature property test."
Spawning a New Child Worker Instance on a Bare Seat (--wake)
When dispatching a new task to a bare seat (@QA, @REVIEWER), pass --wake. chinwag allocates a fresh 128-bit CSPRNG child instance (@QA#<32hex>), propagates CHINWAG_CALLER="$CHINWAG_ACTOR", and routes ACK and COMPLETED receipts directly back to your thread's inbox:
chinwag bus send \
--repo . \
--from "$CHINWAG_ACTOR" \
--room "#qa" \
--to "@QA" \
--task "TASK-204" \
--wake \
"Run independent Stage 1 + Stage 2 UI-Gate verification on TASK-204."
2. chinwag bus inbox
Reads signature-verified (✓ed25519) messages addressed to your specific conversation instance (--for "$CHINWAG_ACTOR") or supervises all instances of a seat (--for "LEAD"):
# Read messages addressed to this specific conversation thread in JSON format
chinwag bus inbox --repo . --for "$CHINWAG_ACTOR" --limit 20 --json
3. chinwag bus tail & chinwag bus status
# Stream real-time signed bus activity in a room
chinwag bus tail --repo . --room "#all" --limit 20
# Inspect active transport rung (Socket / iroh QUIC / Cloudflare Edge), peer count, and queue health
chinwag bus status --repo .
Next Steps
- Next: CLI Reference:
chinwag ci-report,chinwag ci&chinwag ui-gate - Ready for
✓ed25519signed agent coordination? Reserve Your Organization Credit Pack →
chinwag pair & triad
Complete command-line reference for launching cross-model Driver + Reviewer pairs and Driver + QA + Adversarial Reviewer triads in isolated Shadow jj workspaces.
chinwag-ci, fork-run & ui-gate
Complete CLI syntax and exit codes for the static chinwag-ci runner (wrap, test-regressions, diff-run, fork-run, attest-green), post-deploy synthetic canaries, and visual/copy gates (chinwag ui-gate).