NeoShell Note
Why NeoShell Uses neosh After SSH Bootstrap
Why does NeoShell keep SSH for bootstrap but use neosh for the interactive terminal session?
NeoShell uses SSH to establish trust and start neoshd, then uses neosh over QUIC so the interactive session can survive mobile network changes.
Short answer
NeoShell separates two responsibilities: SSH establishes trust and launches neoshd, while neosh carries the interactive terminal over QUIC with explicit detach and resume behavior.
That split preserves the SSH path users already trust without tying the working shell to one fragile TCP connection. For the broad protocol definition and install entry point, see the neosh transport page.
Why NeoShell separates bootstrap and transport
NeoShell starts with the SSH path you already trust. That bootstrap step locates and launches neoshd, then returns the endpoint and identity material needed for the next stage.
After bootstrap, the interactive shell runs over QUIC. That separation lets the session survive conditions that would normally terminate a TCP-bound terminal session.
- SSH bootstrap establishes trust and starts the server-side runtime.
- QUIC carries the interactive terminal session after bootstrap.
- Detach and resume are explicit session behaviors, not an afterthought.
When it helps
neosh helps most when a remote workflow should continue through short interruptions instead of resetting every time the network path changes.
It fits especially well for AI-assisted remote work from iPad, where losing one shell can also mean losing the context around builds, logs, and generated output.
- Wi-Fi to hotspot or cellular switching
- sleep and wake cycles on mobile devices
- lossy networks that cause short transport drops
When SSH alone is enough
SSH alone is still a good answer for stable environments, simple admin tasks, and workflows that already expect reconnect to create a fresh shell.
If your main need is process persistence inside a host login, tmux or zellij may already solve enough of the problem.
FAQ
Does neosh replace SSH?
No. NeoShell uses SSH to bootstrap trust and launch neoshd, then moves the interactive session onto a resumable transport.
Do I still need tmux or zellij with neosh?
Sometimes. neosh helps with transport-level continuity, while tmux and zellij still help if you want a multiplexer-oriented workspace.
When is plain SSH enough?
Plain SSH is often enough on stable networks or when reconnecting to a fresh shell is acceptable.