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
The PR routes lane launches and restart paths through lclaude when installed, while retaining a lane-explicit pclaude --lane fallback for mixed-version environments. Regression coverage simulates the launcher and verifies both user-facing restart guidance and direct tmux pane respawn commands.
File-Level Changes
Change
Details
Files
Prefer the lane-aware launcher for lane startup, handoff restarts, and direct pane respawns, with an explicit fallback for environments without it.
Select lclaude when available for lane-aware launches and restarts.
Fall back to pclaude --lane <lane> rather than bare profile-only pclaude to preserve lane targeting across mixed installations.
Update restart output and respawn commands to reflect the selected launcher.
lane lane-handoff
Extend helper regressions to verify lclaude selection and lane argument placement.
Add a fake lclaude executable to simulate its presence and capture invocations.
Assert handoff output uses lclaude for installed-launcher cases.
Assert direct respawn uses lclaude --lane <lane> <profile> when lane is unavailable on PATH.
Retain rollout compatibility by falling back to explicit pclaude --lane <lane> <profile> when lclaude is unavailable, avoiding bare profile-only pclaude restarts.
Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment @sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment @sourcery-ai review to trigger a new review!
die "the record is written and there is neither \`lane\` nor a launcher on PATH (pclaude, claude-profile), so this pane was NOT respawned. Start the lane yourself: $restart_cmd" 2
die "the record is written and there is neither \`lane\` nor a launcher on PATH (lclaude, pclaude, claude-profile), so this pane was NOT respawned. Start the lane yourself: $restart_cmd" 2
[ -n "$profile_name" ] ||
die "the record is written and this lane's record names no profile, so the launcher cannot be told which account to come up in and the pane was NOT respawned. Start it yourself, naming the profile: pclaude --lane $lane <profile>" 2
die "the record is written and this lane's record names no profile, so the launcher cannot be told which account to come up in and the pane was NOT respawned. Start it yourself, naming the profile: $restart_cmd" 2
This header now advertises lclaude as the default, but the late-handoff instructions immediately above still tell operators to run bare pclaude <profile>. That is inconsistent with the implementation and can send a mixed-version installation through profile-only pclaude; update the late-handoff guidance to use lclaude and the explicit pclaude --lane fallback.
The reason will be displayed to describe this comment to others. Learn more.
Honor PCLAUDE when selecting the restart command
When PCLAUDE explicitly selects pclaude or another launcher while lclaude also exists on PATH, this unconditional probe makes the printed plain/late handoff command use lclaude instead. The automatic --restart path still honors PCLAUDE at line 1160, so the READY message and failure remedies can name a different launcher from the one actually configured and executed; derive this choice from PCLAUDE before probing PATH.
The reason will be displayed to describe this comment to others. Learn more.
Include the profile in the pclaude fallback
On the older installations for which lclaude is unavailable, the suggested fallback omits the required profile argument. The implementation itself constructs pclaude --lane <lane> <profile>; following this canonical lane manual literally therefore cannot select the intended account. Spell the fallback as pclaude --lane <lane> <profile>.
Bring in #81 (lane-rename and the lane alias table), #129, #131, #133,
#135 and #136 so the PR is mergeable again. Two textual conflicts, both
resolved so each side's intent survives:
- lanes-edit.sh, the `*)` arm's unknown-subcommand list: main added
`rename-lane`, this branch added `duplicate-holder`. The list now
carries both, which is what test_repo_hygiene's derived-list check
demands of the dispatcher.
- tests/test_lane_helpers.sh, the suite's fakebin: main added a fake
`gh` (Copilot round 7 on #81), this branch added fake `pgrep` and
`ps` (issue #39). All three fakes are kept and the one chmod line
marks all five fakebin entries executable.
No new main code calls pgrep or ps, so the suite-wide fakes change
nothing for main's new cases; and main's file-keyed LOG_AWK lane field
leaves holder_is_dead's verb-only read and superseded_by's tolower
comparison unchanged in meaning.
Lane: openRepoTools-3
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…#131#133#135#136): one cap conflict, settled at the count of what merged
One textual conflict, the AGENTS.md line cap in
tests/test_repo_hygiene.py: this branch raised 265 to 278 for Amendment
18's ONE BINDING rule, and #119 raised the same 265 to 292 for the
cycle's three rulings. AGENTS.md itself auto-merged to 305 lines,
265 + 13 + 27, with both paragraphs whole and #135's profile-only guard
sentence beside them. So the cap is 305, with a dated MEET AT entry in
the form the 224 entry's rule asks for, rather than either side's
number.
Everything else auto-merged and was read for meaning, not just for
markers. #135 hoists the global-flag parse in lanes-edit.sh above the
path probes and exits 0 for `guard` under exact CLAUDE_NO_LANE=1; this
branch's guard clauses (d) and (e) sit inside the guard, after that
exit, which is right because a profile-only session holds no binding.
Every positional read between the new and old parse sites is inside a
function. #129's lclaude-first launcher in `lane` is the one this
branch's elsewhere and available paths already call. #133's
stable_lane_row and #129's lclaude fakes are cases of their own and
touch none of this branch's.
Lane: openRepoTools-3
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bring #97 onto a current base before the seam rework Brett Heap ruled on
2026-10-04 ("managed ledger owns enrolled lanes; #97 owns legacy — rework
both"). Main moved 14 commits past 957a26f, to daed209: #81 lane-rename,
#83 Amendment 18, #93 Amendment 19, #61 claim --force takeover, #146,
#119, #101-#103, #129, #131, #133, #135, #136, #139 and #134.
Four files conflicted, and in every one both intents survive:
- lanes-edit.sh, the function sections: both sides appended after
migrate_state_cells. Main's Amendment 19(c)/(d) sweep and archive stay
directly under it, because its header says "the shape
`migrate-state-cells` has one screen up"; #97's lifecycle and
inventory section follows them.
- lanes-edit.sh, the unknown-subcommand refusal: the union of both lists,
56 names, the same set as the dispatcher's 56 arms.
- lanes-edit.sh, the exit-code table, and the manual's copy of it: #97's
7 row ("another act got there first", in three verbs) is kept, and exit
9 now has two meanings, one per verb. #61 spent 9 on `claim --force`'s
abandoned takeover and #97 spent it on `lane-state`'s unreadable
snapshot, and each PR took it as unused. Neither verb can return the
other's 9, so the table names both and nothing is renumbered in a
merge. The manual's 9 row said "(`claim` only)", which the merge would
have made false; its 7 row now names #97's two fenced writers too, as
the code table already did. The next commit moves #97's 9 to 10.
- lane-handoff, the late-record restart line: #129's
`$lane_profile_word` (lclaude) with #97's lifecycle line under it.
- docs/README-lanes.md: Amendment 19's section, then #97's #91 section,
so the amendment sections stay in number order.
- tests/test_lane_helpers.sh: main's Amendment 19 and Amendment 18
sections run first, in main's order (A18's restores its fixtures), and
#97's self-contained #91 section follows them, before the
workstation-seam section, as it did on #97's branch.
lane-start auto-merged around #134's rewrite. #97's section 4a still
prints the reconciliation after Amendment 18's binding gate and before
section 5 and the STARTED/RESUMED write in 5b. AGENTS.md, README.md,
tests/test_repo_hygiene.py and skills/ are byte-identical to main, so
the 316- and 486-line caps already match the merged counts.
Locally, tests/run.sh -k 'lane_helpers_suite or repo_hygiene or
lane_start_claude_current or guard_launch_mode or install_skill_and_hook':
274 passed, 600 deselected, in 1560 s.
Lane: openRepoTools-3
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
Summary
lclaudefor lane launches, handoff restarts, and direct pane respawns.pclaude --lanewhenlclaudeis not installed, so mixed versions never restart a lane through bare profile-onlypclaude.Lane: workBenches-lclaude-1
Claim: #128 (comment)
Closes #128
Summary by Sourcery
Use lane-aware
lclaudecommands for launches and restarts while retaining explicitpclaude --lanecompatibility for installations withoutlclaude.New Features:
lclaudefor lane launches, handoff restarts, and direct pane respawns, with explicit lane-awarepclaudefallback support.Bug Fixes:
pclaudecommands.Enhancements:
Documentation:
lclaude-based restarts and thepclaude --lanefallback.Tests:
lclaudeis selected when available for handoffs and pane respawns.