osewa — faster than ssh, survives like mosh, never garbles

The terminal protocol for the age of agents.

Your agent runs for hours on the host; check in from a laptop or a phone, on any network.$ history 1995 ssh devbox 2012 mosh devbox 2026 osewa attach devbox$ ▍▼ PRESS ↓ OR SCROLL TO START§1 Why nowselect your protocolssh and mosh were built for networks we no longer have.ssh 1995The session is its TCP connection: it dies when the network changes, and each key waits behind the download.ROAMINGECHO / LOADFIDELITYmosh 2012Survives roaming, but its own emulator can garble your screen.

UDP only, no forwards, no scrollback.ROAMINGECHO / LOADFIDELITYosewa 2026The session lives on the host with Ghostty's engine.

Forwards and exec share the connection, over QUIC or TCP.ROAMINGECHO / LOADFIDELITY§2 Benchmarkskey echo while a download runsOn a bad network, keys echo 8–100× faster than ssh.Cellular60 ms · deep bufferosewa 138 msssh 1,714 ms12×COMBOWi-Fi20 ms · 1% lossosewa 44 msssh 374 ms8×COMBO1 Mbit/s100 ms · 1% lossosewa 154 msssh no echo in 15 s →>100×COMBO§3 World 2 · public internetThailand → TokyoThailand to Tokyo, over the public internet.CONNECT + RUN A COMMAND · LOWER WINSosewa QUIC311 msosewa WS511 msssh1,337 msmosh1,993 ms§4 Resourcesthe red bar is the winner, even when it's sshLight when idle. Honest about the cost.Host memory, idlelower is betterosewa14.3 MBmosh20.6 MBssh27.4 MBClient memory, idlelower is betterosewa6.9 MBmosh14.3 MBssh8.2 MBHost CPU per MB, log tail50 kB/s · ssh wins hereosewa302 msmosh434 msssh66 msHost CPU per MB, floodoutput as fast as it comesosewa6 msmosh45 msssh12 ms§5 Quick startLinux and macOS hostsssh once. osewa after that.$ osewa login --service me@devbox # install, enroll, run as a service$ osewa attach devbox # attach to (or create) a session$ osewa forward devbox 3000 # forward localhost:3000$ osewa exec devbox -- make test # run a command, no terminal$ osewa update devbox # upgrade the host over osewa§6 Roadmapworld mapA transport any terminal can ride, then a mux on top.✓M0Wire protocol v0✓M1Sessions that survive✓M2Agent-awareM3YOU ARE HEREThe osewa CLIM4nextIn the Moshi appM5laterMuxM6laterEvery screen§7 How it worksSeparate the session from the transport. Then make it hard to kill.01 · HYBRID CARRIERQUIC and TLS WebSocket, raced on every connectQUIC gets a 300 ms head start; if UDP is blocked, the WebSocket wins. Nothing to configure.02 · HOLDERConnections come and go. The session stays.One process per session on the host keeps the PTY, the screen and your unacked input.03 · FLIGHT CONTROLA download can't bury your echoKeystrokes go ahead of bulk, and a slow link gets the latest screen, not a backlog.QUIC · UDP · 1 RTTTLS WS · TCP · +300 ms§8 Agentsfinal levelThe agent keeps working. You check in when it needs you.OSC 7501 · devbox:mainclaude-code ● needs input · 2m ago"Run migrations on staging?

[y/n]"ALL LEVELS CLEAR.