Our take
Maintaineda few commits in the last 90 days- Activity
- 30
- Community
- 19
- Issues
- 21
- Pull requests
- 46
+19 stars in the last 30 days
sshx is a focused option for live terminal collaboration, but its recent activity is light and most development depends on one contributor.
Good fit if
- You want a quick browser-based way to share a terminal for pairing or debugging.
- Your workflow benefits from shared cursors, multiple terminal windows, or temporary access to a CI session.
- You are comfortable using the hosted service and the MIT-licensed project.
Look elsewhere if
- You need a supported self-hosted deployment, which the README says is not currently available.
- You need evidence of frequent releases or broad contributor ownership: there has been no release in over a year, and most of the code comes from one person.
- You need active issue resolution: no issues were closed in the last 90 days, despite some recent commits and merged pull requests.
All health signals
| Last commit | 2026-09-21 (16 days ago) |
|---|---|
| Commits, last 90 days | 2 |
| Releases, last 12 months | 0 (latest v0.4.1, 2025-02-12) |
| Contributors | 6 (top contributor: 98% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 2 |
| Project age | 4 years |
Checked on 2026-10-08 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
7,716Forks
318Change since Nov 14, 2026: 0 stars·0 forks
Overview
sshx is a Rust-based tool for sharing a live terminal with other people through the web. It addresses the friction of coordinating over a terminal session by letting collaborators view and interact with shared terminal windows in real time.
It is aimed at developers who need a quick shared session, such as pairing remotely or inspecting a running CI job. The project operates a hosted service; its README says self-hosted deployment is not supported at the moment.
Key Features
- Start a shared session with a single command.
- Arrange multiple terminal windows on an infinite canvas, then resize, move, zoom, and pan.
- See collaborators' cursors move in real time.
- Use end-to-end encryption based on Argon2 and AES.
- Reconnect automatically and view real-time latency estimates.
- Use predictive echo to make local editing feel more responsive.
- Connect to a nearby server in a globally distributed mesh.
Use Cases
- Remote pair programming, where collaborators need to inspect and work in the same terminal session.
- Debugging a difficult issue together without passing terminal output back and forth.
- Temporarily opening a terminal from a CI job so a developer can investigate a failing build while it runs.
- Sharing a terminal from a small or embedded Linux device, which the project lists among its supported platforms.
What you need
Detected in the repository
- Node.js (from package.json)
- Rust (from Cargo.toml)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install and run the client with:
curl -sSf https://sshx.io/get | sh
For a temporary session without installing first, see the README for the run option and platform-specific details. Visit sshx.io to learn more.
Alternatives
- zellij: Zellij organizes shells in terminal panes and tabs, while sshx shares a live terminal session through a browser.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| sshx | Rust | MIT | 7.7k | Maintained |
| zellij | Rust | MIT | 35.7k | Active |
Considerations
The project is marked maintained, but activity in the recent period amounts to only a few commits, with no release in over a year. Contributor activity is highly concentrated in one person, and no issues were closed in the last 90 days, so teams should weigh the risk of depending on a small maintainer base and slow issue handling.
Self-hosting is explicitly unsupported. The README says deployment requires correctly handling reverse proxies, gRPC forwarding, TLS termination, private mesh networking, and graceful shutdown. It also warns against running the development setup in public because it is insecure, and cautions that public CI logs can expose a live session URL.
Found this useful?
Share it with someone who would like sshx.