Conversation
… "spawn last" "spawn connect" is not a valid top-level CLI command — users following this guidance after SSH reconnect failure would see "Unknown agent or cloud: connect". Replace with "spawn last" which correctly reconnects to the most recent spawn. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
la14-1
force-pushed
the
fix/ux-reconnect-command-suggestion
branch
from
9ab0785 to
02ff629
Compare
louisgv
approved these changes
Apr 16, 2026
Member
louisgv
left a comment
louisgv
left a comment
There was a problem hiding this comment.
Security Review
Verdict: APPROVED — Clean UX fix
Commit: 02ff629
Changes
- Fixed incorrect reconnect command suggestion from "spawn connect" to "spawn last"
- Version bump: 1.0.14 → 1.0.15
Security Analysis
- No injection risks: Simple string literal change
- No credential handling: User-facing message only
- No command execution: Log message, not shell invocation
- No data validation issues: Hardcoded strings
Tests
- bun test: ✅ PASS (2070 tests, 0 failures)
- bash -n: N/A (no shell scripts modified)
Recommendation
Safe to merge — This is a trivial UX improvement with zero security implications.
-- security/pr-reviewer
la14-1
pushed a commit
that referenced
this pull request
Apr 16, 2026
Two user-facing reconnect hints missed by #3311 still showed 'spawn connect <name>', which is not a registered command. Users following the hint get 'Unknown agent or cloud: connect'. Agent: code-health Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
AhmedTMM
added a commit
that referenced
this pull request
Apr 19, 2026
Two user-facing reconnect hints missed by #3311 still showed 'spawn connect <name>', which is not a registered command. Users following the hint get 'Unknown agent or cloud: connect'. Agent: code-health Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com> Co-authored-by: Ahmed Abushagur <ahmed@abushagur.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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why: After exhausting SSH reconnect attempts, the CLI tells users "Reconnect manually: spawn connect" — but
spawn connectis not a valid top-level command. Users following this guidance see "Unknown agent or cloud: connect", a confusing dead-end.spawn lastis the correct command to reconnect to the most recent spawn.Changes
packages/cli/src/shared/orchestrate.ts: Replacespawn connectwithspawn lastin reconnect failure messagepackages/cli/package.json: Bump version 1.0.14 → 1.0.15