# Stay late. Stay connected.

> A feature update shouldn't send you back to your shell. The upcoming connection bastion keeps your SSH client connected while late.sh moves you to a fresh backend.

By Mike Clark · Published 2026-10-22 · Updated 2026-10-22

Status: Coming soon · Checked 2026-10-22 · Category: Clubhouse

Tags: late.sh, SSH, connection bastion, updates, reconnecting, Clubhouse

[Canonical HTML article](https://wikked.info/late-news/posts/connection-bastion/) · [Publication llms.txt](https://wikked.info/late-news/llms.txt)

[Connection bastion · PR #707](https://github.com/mpiorowski/late-sh/pull/707)

**Coming soon:** This is a preview of a proposed change. Connection bastion · PR #707 was open when checked on 2026-10-22.
![A terminal stays connected to a glowing yellow bastion while a mint connection leads to the new late.sh backend and a faded branch marks the retired one.](https://wikked.info/late-news/assets/connection-bastion.svg)

Leave late.sh open long enough and you'll know the routine: a feature update lands, but you're still sitting on the old server. Quit, reconnect, and find your way back. Or go away for a while and return to a disconnected terminal when that old server finally shuts down.

The **connection bastion**, coming in [PR #707](https://github.com/mpiorowski/late-sh/pull/707), takes care of that. **Your SSH client stays connected across late.sh backend updates.** When the old server goes away, the bastion reconnects you to a fresh one. No trip back to your shell, no typing `ssh late.sh` again.

![Renu asks for a way to stop manually quitting old production sessions after updates. Mat replies BASTION and links PR #707.](https://wikked.info/late-news/assets/connection-bastion-chat.png)

The old-server shuffle has come up in chat, too. Screenshot supplied October 22.

## Update now, or stay a little longer

When an update is available, a banner lets you know. Press **`q`, then `r`** in the update dialog to move to the new version without closing SSH. **Esc** dismisses the dialog if you'd rather stay put for now; **`q`** in the dialog still means goodbye.

If you're away when the old server is retired, the bastion handles the reconnect for you. A quick handoff may barely register. If it takes longer, you'll see a reconnecting message, followed by a welcome-back banner once you're in.

## One steady connection

The idea is simple: your SSH connection ends at a small, separate service called the bastion. It passes your terminal's input and output to the late.sh app behind it. The app can be replaced while the bastion keeps holding your connection open.

You use an ordinary SSH client. No special reconnect script or new client to install.

Your account stays yours, but **the app starts a fresh session** during the handoff. This doesn't preserve every open screen, draft, or other state held by the old app. It saves you the disconnect-and-log-back-in routine.

For those of us who leave a terminal in the clubhouse all day, that's a welcome bit of housekeeping to stop doing.

---

**Sources:** [PR #707](https://github.com/mpiorowski/late-sh/pull/707), the [connection design](https://github.com/mevanlc/late-sh/blob/35f7c6275ea164a3d1ce221d5e5e15e63d848cb4/devdocs/LATE-CONNECTION-BASTION.md), and the [update dialog controls](https://github.com/mevanlc/late-sh/blob/35f7c6275ea164a3d1ce221d5e5e15e63d848cb4/late-ssh/src/app/quit_confirm/input.rs). Checked October 22, 2026; the PR is open and production cutover is still pending.