Terminals, drives and job progress keep running through updates
When ZeroLog rolls out an update, an open terminal, a drive or SSH session connected with one click, and the progress card of a running job now carry on. Until today each of them broke off or froze.
If you work in the terminal, use a one-click drive or SSH connection, or watch a running job, an update no longer interrupts it. No action needed.
We update ZeroLog several times a day. Each update starts the app a second time and retires the old copy. Three kinds of connection did not survive that switch.
Terminal. An open terminal stayed on the old copy for up to 45 seconds and was then cut. Keys you typed in that gap were lost. Now the terminal moves to the new copy as soon as the update starts. The session in your workspace keeps running, the terminal reattaches within a second, and what you typed in between arrives once, in order.
Drives and SSH with one click. These connections ran through the app, so every update closed them. They now run through a small separate service that updates leave alone. A mounted drive or an open SSH session stays connected.
Job progress. The card of a running Deep Research, /site or /goal job said "Connection lost" after an update and stood still until you reloaded the page. It now continues after the last step it showed, with nothing missing and nothing twice.
Still to do: the browser extension, ZeroLog Link and the desktop of a virtual machine reconnect after an update instead of carrying on.