Skip to content

fix(tui): use correct ssh-proxy CLI args in shell connect and exec - #193

Merged
johntmyers merged 1 commit into
mainfrom
188-fix-tui-shell-connect/johntmyers
Mar 10, 2026
Merged

fix(tui): use correct ssh-proxy CLI args in shell connect and exec#193
johntmyers merged 1 commit into
mainfrom
188-fix-tui-shell-connect/johntmyers

Conversation

@johntmyers

Copy link
Copy Markdown
Collaborator

Closes #188

Summary

  • The TUI handle_shell_connect and handle_exec_command were using --gateway (cluster name flag) to pass the gateway URL, and omitting the cluster name entirely. After the --gateway--gateway-endpoint rename in feat(cli): improve sandbox provisioning status messages and UX #175, this caused ssh-proxy to fail immediately — producing the flash-and-return behavior and eventual terminal corruption.
  • Changed both functions to use --gateway-endpoint for the URL and --gateway for the cluster name, matching the format already used by start_port_forwards and the CLI's ssh_session_config.

Test Plan

  • Manual: launched TUI, pressed [s] on a sandbox, shell session connected successfully.
  • mise run pre-commit passes (all tests, clippy, fmt).

The ProxyCommand in handle_shell_connect and handle_exec_command was
using --gateway for the URL, but after the #175 rename --gateway means
cluster name and --gateway-endpoint is the URL flag. The ssh-proxy
subprocess could not match token mode (no --gateway-endpoint) or name
mode (no --name), so it exited immediately — causing a screen flash
and eventual terminal corruption from rapid suspend/resume cycles.

Use --gateway-endpoint for the URL and --gateway for the cluster name,
matching the format already used by start_port_forwards and the CLI.

Fixes #188
@johntmyers johntmyers added the bug label Mar 10, 2026
@johntmyers johntmyers self-assigned this Mar 10, 2026
@johntmyers
johntmyers merged commit 057f361 into main Mar 10, 2026
14 checks passed
@johntmyers
johntmyers deleted the 188-fix-tui-shell-connect/johntmyers branch March 10, 2026 04:57
drew pushed a commit that referenced this pull request Mar 16, 2026
)

The ProxyCommand in handle_shell_connect and handle_exec_command was
using --gateway for the URL, but after the #175 rename --gateway means
cluster name and --gateway-endpoint is the URL flag. The ssh-proxy
subprocess could not match token mode (no --gateway-endpoint) or name
mode (no --name), so it exited immediately — causing a screen flash
and eventual terminal corruption from rapid suspend/resume cycles.

Use --gateway-endpoint for the URL and --gateway for the cluster name,
matching the format already used by start_port_forwards and the CLI.

Fixes #188

Co-authored-by: John Myers <johntmyers@users.noreply.github.com>
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.

fix(tui): shell connect broken — wrong ssh-proxy CLI arguments after #175 rename

1 participant