coily dispatch: support non-Mac-local environments incl WSL #138

Open
opened 2026-05-28 07:58:25 +00:00 by coilysiren · 0 comments
Owner

Problem

coily dispatch only works reliably on Mac local today. Every variant - headless
and interactive HITL - should work in other environments too. The gnarliest target
is WSL2 (Windows-side Ubuntu), and it is not yet clear that it can be made to work
there at all.

Scope

Get all dispatch variants working off Mac local:

  • Headless dispatch (claude -p fan-out on an issue ref).
  • Interactive / HITL dispatch (let the operator iterate on the spawned session).
  • Both the GitHub and Forgejo issue-ref code paths.

Target environments, in rough order of expected difficulty:

  • Linux native (kai-server, kai-desktop-tower) - likely closest to Mac local.
  • WSL2 (Windows laptop, Ubuntu 20.04 focal). Highest risk. May not be feasible -
    needs investigation before committing. Suspect blockers: process/PTY handling
    for interactive sessions, terminal multiplexing, /mnt vs /home perf split,
    bare-install toolchain gaps.

Acceptance

  • Document which variant works in which environment, with the actual failure mode
    recorded for any combination that cannot be made to work.
  • For WSL specifically: a go / no-go determination backed by a concrete repro, not
    a guess. If no-go, capture why so we stop re-litigating it.

Notes

WSL host specifics are captured in the kai-wsl-env skill (bare Ubuntu 20.04,
no passwordless sudo, manual Linuxbrew, perf-sensitive /mnt vs /home).

## Problem `coily dispatch` only works reliably on Mac local today. Every variant - headless and interactive HITL - should work in other environments too. The gnarliest target is WSL2 (Windows-side Ubuntu), and it is not yet clear that it can be made to work there at all. ## Scope Get all dispatch variants working off Mac local: * Headless dispatch (`claude -p` fan-out on an issue ref). * Interactive / HITL dispatch (let the operator iterate on the spawned session). * Both the GitHub and Forgejo issue-ref code paths. Target environments, in rough order of expected difficulty: * Linux native (kai-server, kai-desktop-tower) - likely closest to Mac local. * WSL2 (Windows laptop, Ubuntu 20.04 focal). Highest risk. May not be feasible - needs investigation before committing. Suspect blockers: process/PTY handling for interactive sessions, terminal multiplexing, `/mnt` vs `/home` perf split, bare-install toolchain gaps. ## Acceptance * Document which variant works in which environment, with the actual failure mode recorded for any combination that cannot be made to work. * For WSL specifically: a go / no-go determination backed by a concrete repro, not a guess. If no-go, capture why so we stop re-litigating it. ## Notes WSL host specifics are captured in the `kai-wsl-env` skill (bare Ubuntu 20.04, no passwordless sudo, manual Linuxbrew, perf-sensitive `/mnt` vs `/home`).
coilysiren added
P4
and removed
P3
labels 2026-05-31 06:59:41 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
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-bridge/coily#138
No description provided.