0.65.0

A session whose saved conversation is gone now starts anyway. Clicking one did nothing at all: no pane, no error, nothing to click again.

A resume key can outlive the thing it points at. Open a session, never type in it, let the idle reaper stop it six hours later, and the CLI has nothing on disk to come back to. CLIque asks for it anyway, the CLI refuses in about a second and a half, and the tab goes quiet.

The panel now watches a resume for up to eight seconds and, the moment the pane turns out to be gone, drops the key and starts the session clean. Usually over in two seconds, and there is nothing to click, learn or turn on. It only does this for a key that is CLIque's own session id, which is the one case where we know how it got there and can derive it again. Stopping a session inside that window wins, so nothing is ever resurrected behind you.

POST /api/sessions/<id>/start now answers with resumed, saying whether the resume form was used.