0.16.0
Sessions now survive the server.
Until this release a session was a dictionary that died with the process: reopening the one you were working in meant nothing, and an identity built up over an hour went with it. What gets saved is the declaration - which browsers a session has, who each one is, and which one your commands were going to.
Not eight live browsers. Eight of those measure 61 processes and about 6.5 GB, with the eighth taking 13.6 s to start, so reopening a session gives the identities back immediately and each engine starts when a command is aimed at it, as the right person. Cookies and logins come back where a browser had a profile directory.
Two new tools: session_list finds the session you were in, and session_forget deletes one and closes its browsers, which is not the same as closing browsers and keeping the session.
Saved sessions live under AIHAWK_HOME (by default %APPDATA%/aihawk on Windows, ~/Library/Application Support/aihawk on macOS, $XDG_DATA_HOME/aihawk on Linux).