fix: make interactive ps:exec sessions feel like heroku console

[tarzan]

Summary

Interactive ps:exec was sluggish and lost the cursor in line editors such as an Elixir remote shell. The built-in SSH client delayed single-byte writes and rewrote carriage returns. Interactive sessions now hand the terminal to system ssh, the same way heroku console does on Private Spaces, and fall back to the built-in client when ssh is not installed.

Type of Change

Breaking Changes (major semver update)

• Add a ! after your change type to denote a change that breaks current behavior

Feature Additions (minor semver update)

• feat: Introduces a new feature to the codebase

Patch Updates (patch semver update)

• fix: Bug fix
• deps: Dependency upgrade
• revert: Revert a previous commit
• chore: Change that does not affect production code
• refactor: Refactoring existing code without changing behavior
• test: Add/update/remove tests

Testing

Notes:
Unit tests cover the terminal passthrough, window size, and the choice between system ssh and the built-in client. A live dyno check still needs a rebuilt CLI.

Steps:

1. npm test for test/unit/lib/ps-exec/ssh.unit.test.ts and test/unit/commands/ps/exec.unit.test.ts.
2. npm run build && ./bin/run.js ps:exec -a <app>, then start the release remote shell and edit a long line.
3. Repeat with stdin piped to confirm the built-in client is still used for non-interactive commands.

Screenshots (if applicable)

Related Issues

GitHub issue: n/a
GUS work item: n/a

Made with Cursor