You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Start a fleet relay session on a Windows lane in a plugin profile #16605
A session the fleet relay starts on a Windows lane (rows R1, R3, R6 of the reach skill) can start in a plugin profile. #16601 delivered this for WSL lanes and left Windows lanes out: a Windows start runs without the profile and says so. Part of #16428.
Why it was left out
profiles.mjs launch prints a command that is a POSIX env -u ... claude --settings <file> line, which a Windows shell cannot run.
What is known
launch --json also prints argv, the same words as an array. The machine-health wrapper (feat(machine-health): start the monthly run in a plugin profile #16590, plugins/machine-health/skills/setup/templates/monthly-run.ps1) starts a profiled run on Windows from argv: it removes each env -u NAME variable from the child's environment and passes the remaining arguments to claude, with no env.
The relay section to extend is "Start in the target's plugin profile" in plugins/fleet/skills/reach/reference/relay.md.
Done when
The relay section covers a Windows lane: it finds profiles.mjs on the target as it does on a WSL lane, runs launch ... --unattended --json, clears the variables the printed argv names without env, and starts claude.exe with the remaining arguments.
With no profile named, or no enabled plugin-profiles on the target, a Windows start behaves as it does today and says the profile was not applied.
An unattended start whose profile needs a missing required tool starts nothing and reports the reason.
The Windows route is tried once on a real Windows lane, or the section says it is untested on a live hop.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: extend the "Start in the target's plugin profile" section of the fleet reach relay reference so a session started on a Windows lane (rows R1, R3, R6) runs in the plugin profile. It would use the printed argv from profiles.mjs launch ... --unattended --json: clear the env -u variables, then start claude.exe with the remaining arguments. It also needs the no-profile and missing-required-tool behaviours, and eval cases.
Nothing is missing that blocks triage. The live Windows hop in the fourth done-when item cannot run unattended, so the issue lane can check the other items and the live run stays with the host-run route, or the section states it is untested on a live hop.
This is a follow-up to #16601 (the WSL version) under #16541 and #16428, not a duplicate of an open issue. #16455 (verify the plugin-profiles CLI on the Windows lane) is related but asks for a different thing.
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
Activity
github-actions commentedon Nov 16, 2026
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: extend the "Start in the target's plugin profile" section of the fleet reach relay reference so a session started on a Windows lane (rows R1, R3, R6) runs in the plugin profile. It would use the printed
argvfromprofiles.mjs launch ... --unattended --json: clear theenv -uvariables, then startclaude.exewith the remaining arguments. It also needs the no-profile and missing-required-tool behaviours, and eval cases.Nothing is missing that blocks triage. The live Windows hop in the fourth done-when item cannot run unattended, so the issue lane can check the other items and the live run stays with the
host-runroute, or the section states it is untested on a live hop.This is a follow-up to #16601 (the WSL version) under #16541 and #16428, not a duplicate of an open issue. #16455 (verify the plugin-profiles CLI on the Windows lane) is related but asks for a different thing.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 16, 2026
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).