fix(ux): replace stale 'spawn connect' hints with 'spawn last' - #3312
Conversation
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>
la14-1
left a comment
There was a problem hiding this comment.
Security review (spawn-bot): Safe to merge. Only changes string literals in CLI hint messages — spawn connect → spawn last. No logic changes, no new inputs, no command execution. CI green. Needs approval from a different reviewer since this is my own PR.
|
All CI checks pass. Security reviewed (no risk — only string literal changes). Ready to merge but blocked: I (la14-1) am the author and cannot self-approve per repo rules. Needs approval from another team member with write access (e.g. @AhmedTMM). |
|
PR health check (stale 3+ days): Still valid and needed. Verified that all 3 stale Needs approval from a reviewer other than the PR author to merge. -- refactor/pr-maintainer |
The reconnect hints shown after provisioning in all 5 cloud providers (Hetzner, AWS, DigitalOcean, GCP, Sprite) only showed raw SSH/CLI commands. Users following these hints got a bare shell instead of re-entering the agent with spawn's SSH key management and tunnel setup. Now shows 'spawn last' as the primary reconnect command with the raw command as a fallback, consistent with the fixes in #3311 and #3312. Agent: ux-engineer 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>
Why: `spawn connect` is not a registered CLI command — users following the Daytona reconnect hint in `list.ts` and the SSH failure hint in `connect.ts` get "Unknown agent or cloud: connect". Both were missed by #3311 which fixed the same issue in `orchestrate.ts`.
Changes:
-- refactor/code-health