Repository navigation
AIOS 0.9.1 — closing a session now asks you how
A small release about one irreversible click.
The × on a session tab asks first
Every live session has a tab in the RUNNING strip, and its × used to end the
session immediately. In AIOS that is not a lost process — it is a lost record:
the session never ran /close-session, so the day's note gets no entry for
whatever it did and nothing downstream can reconstruct it. The × and the tab
body are the same button, told apart only by which pixel you hit.
It now asks, and it asks your question — the one already in Settings under
"When you kill a session":
- Ask (capture or kill) — the default. Offers Capture & close (runs
/close-sessionfirst, so the work is written down) or Kill now. The safe
option holds the selection, so a reflex Return captures rather than kills. - Always capture first — the tab stays up while the session wraps itself up.
- Kill immediately — no dialog, exactly as before.
That setting used to govern one control, the trash button on a RUNNING card
session row. Now it governs every way you can end a session by hand: the tab ×,
⌘W, File → Close Tab, and the Terminals row. Programmatic closes are untouched —
the command bus, a session retiring itself, a capture that has landed.
Cancelling puts you back where you were typing, which is the whole point: a
mis-click should cost nothing.
Enter follows focus
Confirmation dialogs focus Cancel — and Return confirmed anyway, whatever was
focused. So the focus ring said Cancel while the keypress destroyed. This affected
deleting a connector and removing a frequent task. Return now activates whatever
actually holds focus.
Under the hood
The app no longer ships its own compiled test suite inside the bundle, and the
packaged artifact is checked for it on every platform rather than trusted to be
clean.
Downloads
macOS (Apple silicon) AIOS-arm64.dmg · Windows AIOS-x64.exe · Linux
AIOS-x86_64.AppImage or AIOS-amd64.deb. Existing installs update themselves.
Full commit list: v0.9.0...v0.9.1