retoorandClaude Opus 4.8
115e403e67
Native WhatsApp Web multi-device client in C++ (src/whatsapp/, namespace detz::wa), built on OpenSSL plus a vendored public-domain ed25519 ref10 (third_party/ed25519, zlib) for XEdDSA and the nayuki QR generator (third_party/qrcodegen, MIT); no new runtime dependency. - WaCrypto, WaBinary, WaProto, WaNoise, WaSignal, WaDevice, WaSocket, WaClient, WaStore, WaQr, WaWizard. - Verified offline against golden vectors captured from the real Baileys client (tests/whatsapp_data, from jfelipesjc/wa-go, MIT): HKDF/PBKDF2 RFC vectors, XEdDSA roundtrips, codec battery 19/19, ClientPayload byte-exact, the Noise handshake, and a 4-exchange Signal session byte-exact. Unit test build/whatsapp_test (16/16), run_all step whatsapp.unit. - Verified live against web.whatsapp.com: `detz --whatsapp-link` connects, completes the Noise handshake, receives pair-device, renders a scannable QR in the terminal, and persists the device to the vault (whatsapp/<profile>.db). Also --whatsapp-status / --whatsapp-unlink. - Agent tools whatsapp_send and whatsapp_contacts (detz-only, in DetzTools). - Pairing completion after the phone scans, and the message send path (usync + prekey fetch + Signal encrypt + send node), are ported faithfully from whatsmeow but unverified in-tree (no linked account in development). send_image and own-device fan-out are not wired yet. See docs/whatsapp.md. Also in this snapshot: the terminal-screenshot tool (src/termshot/, terminal_screenshot, docs/termshot.md, research/terminal-screenshot-rendering) and a concurrent session's in-progress llm/muse failover changes carried along in the shared files. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
detz: C++23 port of tai.py
Future molo detz subcommand. See plan.md, SPEC.md, docs/.
Build: make && make test. Binary: build/detz. Rules for working here: AGENTS.md.
What taicpp adds on top of the port
The port is behavior-compatible with ../tai.py and checked against it (PARITY.md, docs/parity.md).
These parts exist only here; each has a specification and tests:
| Feature | Spec | Code | Tests |
|---|---|---|---|
| Fuzzy matching of identifiers (letter order, word boundaries, typos, trigrams) | docs/fuzzy.md | src/util/fuzzy.* |
build/fuzzy_test |
CAP agents and their models: discovery, probes, @agent, @agent:model, @model |
docs/cap-agents.md | src/cap/cap_model_catalog.*, src/cap/cap_mention.* |
build/capmcp/cap_model_catalog_test |
| Sub agents in live panels on the multiplexer screen, with supervision | docs/orchestration.md | src/orch/, src/mplex/mplex_vpane.* |
build/orch_test, tests/orch_mplex_e2e.py |
Reading order for a new contributor: docs/cap.md (the protocol), docs/cap-agents.md (agents and
models), docs/fuzzy.md (how a mention is matched), docs/mplex.md and docs/orchestration.md (the screen).
Using it
@claude refactor the parser run one turn on a CAP agent (typos are fine: @clde)
@claude:opus review the diff on a specific model of that agent
@opus review the diff a model name alone works when one agent offers it
@claude pin the agent for following messages; @auto clears all pins
Sub agents (fork workers and agent turns) appear in panels on the right of the multiplexer screen while
they work; closing a panel cancels its agent. TAI_ORCH_PANELS=0 turns the panels off.
Tests
make test builds every test binary and runs tests/run_all.py (36 steps, logs in build/test-logs/).
Single steps: python3 tests/run_all.py --only orch, --only mplex, --only capmcp, --only fuzzy.
The research behind the decisions is in ../research/ (index: ../research/INDEX.md).