workflow: dispatch durable agents to paired machines
agent(prompt, {on: "paired-machine", cwd: "/remote/project"}) uses the existing authenticated acpmux dispatch route. Each call persists its exact destination, child session, prompt, execution fingerprint and private receipt capability before dispatch. Replay attaches to that same durable call and reads its exact final reply; schema correction uses its own stable child identity.
Remote agents require an explicit peer: on: "ci" and on: "auto" are refused, and malformed placement values cannot fall back to local execution. Durable receipt replay and cancellation are bound to the initiating local caller plus a per-brief capability. Legacy brief/task listings, steering, reports and advisory peer imports cannot expose or replace another caller's durable receipt. A remote turn's wait survives the ordinary link-request deadline.
This builds on landed executor #33779 (74c166b0130b2267bf1ac07c2f80025e7305e970). The dispatch reservation, receipt authorization and cancellation remain together because they share one stable identity and admission fence. The integration regression uses an authenticated real peer to check that terminal cleanup reaches its pending remote child while preserving a reserved-looking logical sibling. Parent-child matching validates the persisted dispatch fingerprint, canonical activity identity and exact destination/child.
Validation: prepush and whitespace checks pass. Red-before-fix commit 5f8f83e3a71103f78922686afceb9cc515d6977e compiled and executed the focused cancellation regression in run 41658393240, failing exactly with "pending remote child was not cancelled" (one test selected). At reviewed head aef21fb8f640c1ddbee30e9f8a0c4b96343a148f, run 41660111202 passed formatting and all focused remote schema/replay, cancellation, durable dispatch, receipt isolation, turn-wait and placement tests. Strict clippy then failed only the inherited executor collapsible_if at server/workflow_activity.rs:247; #33779 already contains that repair. The final integrated head is 06f7ba85134b5235a002e976a4588a681a3cbf7a; final fleet run 41665788549 passed formatting, focused remote workflow tests, durable dispatch and turn-wait tests, placement coverage, and strict clippy. The exact-head Opus 5.5 medium review carry is SHIP at 06f7ba85. The integrated diff preserves the reviewed remote changes while incorporating landed executor/base modules. No local Cargo builds were run.
Independent review: Opus 5.5 medium SHIP at aef21fb8. Review follow-ups: foreign brief/destination cancellation tests #33969, optional persisted capability validation #33970, constant-time fingerprint equality #33971, status capability redaction #33972, advisory-import authority stripping #33973, and anonymous caller binding coverage #33974.
Limitations and follow-ups: remote stall escalation is tracked in manaflow-ai/cmuxterm-hq#6560. Disconnected-peer cancellation reconciliation is tracked in #33846, including a transport error that has already been recorded as a child outcome and therefore gets skipped by current terminal/pause cleanup (https://github.com/manaflow-ai/cmux/issues/33846#issuecomment-6607099334). This PR's pending-child ownership repair does not implement durable reconnect tombstones. Authenticated machine({on:"ci"}) is a separate adapter tracked in #33778; the peer background-command boundary stays closed. Signing, notarization and publishing secrets stay in Actions.
Leo asked on 2026-11-02: "go do all those/help out where you can + examine how you can improve yourself and your available options and capabilities and speed". This implements paired-agent placement for native workflows in the nightly-train design (Ā§3.2ā3.3; teamleaderleo/leo-workspace#624).
Leo-ask: ask-6ef2624788
š¤ Generated with Codex
Agent session: agent session