fix(warp): repoint interactive-dispatch shim to ward dispatch #217

Closed
opened 2026-06-15 00:28:01 +00:00 by coilysiren · 1 comment
Owner

The Warp interactive-dispatch launch config is repointed from the retired coily dispatch to ward dispatch.

Since coily dispatch was removed (coilyco-bridge/coily#212) and ward dispatch now owns the command in its own .ward namespace (coilyco-flight-deck/ward#86), the shared shim must read ward's queue:

  • claude-dispatch-interactive.sh: QUEUE_DIR -> /tmp/ward-dispatch-queue, and the "did you write one?" hint names ward dispatch interactive.
  • .yaml / .toml header comments updated to ward dispatch (older coily path names noted as historical; the coily#270 design refs kept).

The shim is now ward-only.

The Warp interactive-dispatch launch config is repointed from the retired `coily dispatch` to `ward dispatch`. Since `coily dispatch` was removed (coilyco-bridge/coily#212) and `ward dispatch` now owns the command in its own `.ward` namespace (coilyco-flight-deck/ward#86), the shared shim must read ward's queue: - `claude-dispatch-interactive.sh`: `QUEUE_DIR` -> `/tmp/ward-dispatch-queue`, and the "did you write one?" hint names `ward dispatch interactive`. - `.yaml` / `.toml` header comments updated to `ward dispatch` (older `coily` path names noted as historical; the coily#270 design refs kept). The shim is now ward-only.
Author
Owner

Already landed on main before this was filed: the warp interactive-dispatch shim (claude-dispatch-interactive.{sh,yaml,toml}) was migrated to ward dispatch upstream (QUEUE_DIR=/tmp/ward-dispatch-queue, ward#280). The gish pass found the change redundant on rebase. Closing as already-done.

Already landed on main before this was filed: the warp interactive-dispatch shim (`claude-dispatch-interactive.{sh,yaml,toml}`) was migrated to `ward dispatch` upstream (QUEUE_DIR=/tmp/ward-dispatch-queue, ward#280). The gish pass found the change redundant on rebase. Closing as already-done.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/agentic-os#217
No description provided.