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 reach or relay session in the target lane's plugin profile #16541
A session that /fleet:reach or its relay starts on another lane starts in a plugin profile, the way local launch sites do since #16523. Part of #16428.
Owner decision
2026-11-16, "go w/ recommendations": dotfiles renders each lane's profiles.mjs path into FLEET.md, and the relay gets one "start in the target's profile" section. Recorded on control-hub#11. The FLEET.md part is filed in the dotfiles repository; this item waits for it.
What is known
feat(plugin-profiles): launch each session with its plugin profile #16523's body says why these sites were left alone: the local hops cross the WSL boundary, where only WSLENV variables cross, so the session marker does not leak; a remote start in the remote's profile needs the remote's profiles.mjs path.
profiles.mjs launch <name> --folder <dir> --json prints the argv a launcher runs, and --with merges a launcher's own settings (the relay passes inline --settings JSON today).
Done when
The relay reference has one section for starting the target session in a profile: it runs the target lane's profiles.mjs launch (path from FLEET.md) on the target, merges the relay's own settings through --with, and starts claude with the printed argv.
With no profile named, or on a lane where FLEET.md says plugin-profiles is not installed, the relay behaves as it does today and says the profile was not applied.
An unattended start whose profile needs a missing required tool stops and reports (--unattended).
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: make /fleet:reach and its relay start the target session in the target lane's plugin profile. The relay finds profiles.mjs on the target, runs launch with the relay's own settings merged through --with, and starts claude with the printed argv. With no profile named, or where plugin-profiles is not installed, it behaves as today and says the profile was not applied. An unattended start whose profile needs a missing required tool stops and reports (--unattended). The issue also adds one sentence to the reach skill's prompt-writing line, and tests cover both paths.
The owner's recorded decision settles the open design question:
Decision recorded. Owner, 2026-11-16: "go w/ recommendations" (control-hub#11). This item no longer waits on dotfiles: the relay finds the target lane's profiles.mjs by running claude plugin list --json on the target and taking the installPath of the enabled plugin-profiles@… entry, as find_profiles_script in plugins/harness-ops/skills/lanes/scripts/lane-launcher.sh does. FLEET.md renders no path; dotfiles#1626 is closed as not planned. Read any line in this issue's body that names a rendered FLEET.md path as replaced by this.
That decision settles every open question, so nothing more is asked. The host-run label still holds admission until it is met. I found no likely duplicate or merged fix. #16542 is a sibling item, not a duplicate, and #16428 is the parent.
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).
Added scope, decided by the hub session "Plugin Presets" (owner decision Q4, 2026-11-16, recorded on control-hub#11): the reach skill's line on writing a prompt (plugins/fleet/skills/reach/SKILL.md, "Give every prompt the whole task") also says to get the name of the session that holds a PR, issue or branch and put it in the prompt, and never to tell the target to take the work over on its own judgment. One sentence, in the same pull request as the relay section. The dotfiles side is dotfiles#1629.
Decision recorded. Owner, 2026-11-16: "go w/ recommendations" (control-hub#11). This item no longer waits on dotfiles: the relay finds the target lane's profiles.mjs by running claude plugin list --json on the target and taking the installPath of the enabled plugin-profiles@… entry, as find_profiles_script in plugins/harness-ops/skills/lanes/scripts/lane-launcher.sh does. FLEET.md renders no path; dotfiles#1626 is closed as not planned. Read any line in this issue's body that names a rendered FLEET.md path as replaced by this.
Activity
github-actions commentedon Nov 16, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: make
/fleet:reachand its relay start the target session in the target lane's plugin profile. The relay findsprofiles.mjson the target, runslaunchwith the relay's own settings merged through--with, and startsclaudewith the printed argv. With no profile named, or where plugin-profiles is not installed, it behaves as today and says the profile was not applied. An unattended start whose profile needs a missing required tool stops and reports (--unattended). The issue also adds one sentence to the reach skill's prompt-writing line, and tests cover both paths.The owner's recorded decision settles the open design question:
#16541 (comment) is the added-scope comment. The decision comment is #16541 (comment).
That decision settles every open question, so nothing more is asked. The
host-runlabel still holds admission until it is met. I found no likely duplicate or merged fix. #16542 is a sibling item, not a duplicate, and #16428 is the parent.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).kyle-sexton commentedon Nov 16, 2026
Added scope, decided by the hub session "Plugin Presets" (owner decision Q4, 2026-11-16, recorded on control-hub#11): the reach skill's line on writing a prompt (
plugins/fleet/skills/reach/SKILL.md, "Give every prompt the whole task") also says to get the name of the session that holds a PR, issue or branch and put it in the prompt, and never to tell the target to take the work over on its own judgment. One sentence, in the same pull request as the relay section. The dotfiles side is dotfiles#1629.kyle-sexton commentedon Nov 16, 2026
Decision recorded. Owner, 2026-11-16: "go w/ recommendations" (control-hub#11). This item no longer waits on dotfiles: the relay finds the target lane's
profiles.mjsby runningclaude plugin list --jsonon the target and taking theinstallPathof the enabledplugin-profiles@…entry, asfind_profiles_scriptinplugins/harness-ops/skills/lanes/scripts/lane-launcher.shdoes. FLEET.md renders no path; dotfiles#1626 is closed as not planned. Read any line in this issue's body that names a rendered FLEET.md path as replaced by this.github-actions commentedon Nov 16, 2026
The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).
feat(fleet): start a relay session in the target lane's plugin profile