# Osewa keeps remote terminals running when networks change > Source: > Published: 2026-11-04 10:34:27+00:00 # Osewa keeps remote terminals running when networks change **Built by the developer behind Moshi, Osewa keeps terminal sessions and agent status on the host over QUIC or TLS WebSocket, with SSH used only for setup.** By [RuntimeWire Staff](https://runtimewire.com/author/runtimewire-staff) · Published Primary source: [Hacker News](https://osewa.dev/) ## Why it matters For long-running coding agents, a remote terminal needs to preserve the session, screen and pending approval through sleep, roaming and blocked UDP for hours. Osewa tests whether an open protocol built on Ghostty's engine, QUIC with TCP fallback and explicit agent status can replace the SSH-plus-tmux workaround developers use to check on that work. The developer behind GitHub account [rjyo](https://github.com/rjyo?ref=runtimewire), listed there as Joel, is building [Osewa](https://osewa.dev/?ref=runtimewire) around a familiar failure: a coding agent keeps working on a remote host while the person checking on it moves between networks. Osewa describes that workflow directly, saying "your agent runs for hours on the host" and the user can "check in from a laptop or a phone, on any network." Joel's public GitHub profile also centers on Moshi, including a Homebrew tap for Moshi and terminal tooling for use with the app.… When you purchase through links in our articles, [we may earn a small commission](https://runtimewire.com/affiliate-monetization-standards). This doesn’t affect our editorial independence.