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
fix(terminal): scope account restart metadata to its execution host - #34214
Account restarts now select the workspace folder and repository connection from the pane’s execution host when IDs repeat across hosts.
What Changed
Resolve the execution host before selecting the restart workspace, and pass it to both workspace lookups.
Match the repository by its ID and that same host with the existing owner-only identity predicate.
Add two regression cases with local-first duplicate IDs: resume changes to the recorded session folder when needed, while a saved tab start folder retains priority. The real launch-target function also receives the selected repository connection.
Why
A bare-ID lookup can mix one host’s folder or repository connection with another host’s launch target, causing a wrong working directory or platform. The owner-only predicate cannot fall back to the active-server setting.
Linked Issue
Found while validating module organization. The preceding compile/import repairs have landed in #34202; this PR contains only the remaining host-ownership fix.
Visual Proof
N/A — launch planning only; no rendered layout changes.
Testing
Added meaningful regression coverage
Manual app testing
Both defects were reproduced before their repairs. On the final rebased head, 56 tests across three restart suites and all 21 changed-file checks pass. Two independent source reviews confirm that the upstream workspace-fallback regression and fixture reset are preserved. All 34 hosted CI contexts completed successfully or were skipped as inapplicable, with the aggregate check green. Final independent merge admission also passed.
Review
Preserves lazy folder fallback, saved tab-folder priority and existing launch quoting. Uses existing workspace and repository identity owners. No gate, baseline, assertion or type suppression changes.
Agent skill upstream boundary
Not applicable; no upstream skill-installer material copied.
Checklist
Cross-platform, remote, folder and mobile launch behavior considered
Two-file behavior repair; zero module-organization tracker credit
Final independent reviews, validation and required CI complete
nwparker
changed the title
fix: restore restart fallback and browser-link test state
fix: restore account restart fallback and stale test fixtures
Oct 27, 2026
Resume startup now uses the worktree’s execution host when looking up the worktree and matching its repository. Tests cover workspace-folder and saved-tab-folder Claude resume cases with a remote execution host, including the selected host and SSH connection passed to the resume-target resolver.
Priority: Normal
Merge Risk: Low · up to fc257
The host-scoping fix is in place. Clear the test spy between cases so the saved-tab regression test independently verifies its resolver call.
Pre-merge checks: 4 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Docstring Coverage
Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surv…
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks: 4 passed
Check name
Status
Explanation
Title check
The title clearly and concisely describes the main change: scoping account restart metadata to the execution host.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The description covers the core change clearly: it explains that account restarts now pick the workspace folder and repository connection from the pane's execution host, lists the code-level changes, …
Full details: Description check
Explanation
The description covers the core change clearly: it explains that account restarts now pick the workspace folder and repository connection from the pane's execution host, lists the code-level changes, and gives the reason (a bare-ID lookup can mix one host's folder or repository with another host's launch target). It also includes testing evidence and a review note. The template's required sections are all present. Gaps: the Linked Issue section has no issue number ("Fixes #" is blank) and describes a stacked PR instead, which the template says outside contributors must link. The Testing section says manual app testing is unchecked, and the template asks for steps a reviewer can follow and the platforms tested. The Visual Proof section says N/A with a reason, which fits the template. The Checklist omits several template items, including the lint, typecheck, test and build confirmation. The AI Disclosure section is empty. Overall, the description is mostly complete with some gaps in linking and testing detail.
Full details: Docstring Coverage
Explanation
Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 2 functions across 2 files.
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
Finishing Touches: 💡 1
📝 Generate docstrings: 💡
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.
nwparker
changed the title
fix: restore account restart fallback and stale test fixtures
fix(terminal): scope account restart metadata to its execution host
Oct 27, 2026
The fixture has host-colliding worktrees, but the test does not assert /remote/workspace. Both command assertions use the session cwd or saved tab folder, so an unscoped lookup can pass.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.
Clear the resolver spy before each parameterized case.
clearMocks is disabled. The saved-tab-folder case uses toHaveBeenLastCalledWith, so it can reuse the workspace-folder case’s previous call if the resolver stops running. The command assertion does not verify that the resolver was called.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 5 remain after this review.
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.
ELI5
Account restarts now select the workspace folder and repository connection from the pane’s execution host when IDs repeat across hosts.
What Changed
Why
A bare-ID lookup can mix one host’s folder or repository connection with another host’s launch target, causing a wrong working directory or platform. The owner-only predicate cannot fall back to the active-server setting.
Linked Issue
Found while validating module organization. The preceding compile/import repairs have landed in #34202; this PR contains only the remaining host-ownership fix.
Visual Proof
N/A — launch planning only; no rendered layout changes.
Testing
Both defects were reproduced before their repairs. On the final rebased head, 56 tests across three restart suites and all 21 changed-file checks pass. Two independent source reviews confirm that the upstream workspace-fallback regression and fixture reset are preserved. All 34 hosted CI contexts completed successfully or were skipped as inapplicable, with the aggregate check green. Final independent merge admission also passed.
Review
Preserves lazy folder fallback, saved tab-folder priority and existing launch quoting. Uses existing workspace and repository identity owners. No gate, baseline, assertion or type suppression changes.
Agent skill upstream boundary
Checklist