Skip to content

Launch pane-started Nod loops with their lineage, like the daemon - #607

Merged
scgopi merged 1 commit into
mainfrom
fix/nod-pane-lineage
Oct 3, 2026
Merged

scgopi merged 1 commit into
mainfrom
fix/nod-pane-lineage

Conversation

@scgopi

@scgopi scgopi commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Follow-up from the #600 review: a Nod loop whose session the app pane starts (a turn-based fork, or a pane that wins the race with graphcoded) launched without its lineage.

Change Detail
GhosttyTerminalView.lineage Passed from the loop in LoopWorkspaceView
nodLaunchPrefix(fresh:) --inherit <brief> on a fresh start only; --unattended for timed loops and composite children, matching ZmxSessionLauncher.nodArguments
resumeCommand Asks for the prefix with fresh: false, so a resumed conversation never replays its brief

Evidence

RED: NodLaunchArgumentTests.aPaneStartedNodLoopCarriesItsLineageLikeTheDaemon on origin/main -> compile failure, GhosttyTerminalView has no lineage and launchPrefix no fresh: parameter
GREEN: xcodebuild test -only-testing NodLaunchArgumentTests + CopilotVersionTests -> exit 0, 23 tests passed
REGRESSION: full xcodebuild test -> 2211 tests, only MessageDeliveryTests.aSessionWhoseTaskEndedIsNeverTypedInto fails, which fails identically on main on this Mac; cli and daemon builds exit 0; make check 0 errors; swift-portable exit 0

A pane can start a Nod session before graphcoded does. It now passes the
lineage brief with --inherit on a fresh start only (never on resume) and
launches a composite child --unattended, matching
ZmxSessionLauncher.nodArguments.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: scgopi <scgopireddy@gmail.com>
@scgopi
scgopi merged commit 1c5e303 into main Oct 3, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant