ConnectOnion 1.9.3rc38 (release candidate)
Stable remains 1.9.2; Python 3.11+ and the existing dependency floors are retained.
co init sets up REM
- Global
co init(no path) now ends with the REM first run, in-process. When no mailbox is connected it offersco auth google/co auth microsofton the spot; it shows which sources will be read, with which model, on which schedule and under which daily cap, and asks once; it installs upkeep and says which scheduler it installed (Codex Scheduled task or launchd); then it maps the last 180 days and builds the first notebook (#2755). - The estimate pauses once in a terminal:
Build the first map now? [Y/n], default yes.nkeeps upkeep installed and printsco rem initfor later. The same pause applies toco rem init;--yesand non-tty runs keep the old behaviour (#2752 item 5). co init --yesand non-tty runs create REM storage only and print the two auth commands; they grant no consent and schedule nothing.co init --no-remskips REM. A secondco initsays REM is already initialised and changes nothing.co init --backgroundno longer creates REM storage without consent; it runs the same step.- Session summaries, a model call per recent coding session, now run after the pause instead of in parallel with the mail download, so nothing is spent before the question. A fresh map takes a few minutes longer.
Also since 1.9.3rc36
co rem init --helpuses a fictional example;co rem --helpsays "1.9.x" instead of "before 1.9.0"; a mailbox that was never connected is reported as "waiting for co auth google / microsoft" rather than "unsubscribed" (#2753).
Install after publication
python -m pip install --upgrade 'connectonion==1.9.3rc38'
ConnectOnion