Repository navigation
v0.164.10
Install or update: npm i -g cotal-ai@0.164.10
Restart running Cotal processes and agent sessions to use the new code.
What changed
- The desktop app's Details no longer tells you to install the background service when it is already installed and stopped.
- Add verified execution generations to the CLI entry without changing the update transaction.
- Keep the installed Windows background service running after a manual update.
- A host can replace one space's account record without rewriting the broker record every space shares.
- Keep a running command's release identity tied to the code it loaded during staged updates.
Every change in full
-
The desktop app's Details no longer tells you to install the background service when it is already installed and stopped. It now says the service is stopped and that Start service starts it. A computer with no installed service keeps the install sentence.
-
Add verified execution generations to the CLI entry without changing the update transaction.
The built-ins-only bootstrap accepts an artifact-bound descriptor, validates the retained package inventory and runs the selected generation. Fresh installations run their installed tree without copying it or writing startup state. Invalid matching descriptors refuse with reinstall guidance.
-
Keep the installed Windows background service running after a manual update.
The replacement updater starts only its verified enabled scheduled task after the old daemon exits, and checks target readiness under the existing deadline. Windows updater ownership uses retained process creation identity, including guarded compatibility with published records that lack a start token.
-
A host can replace one space's account record without rewriting the broker record every space shares.
replaceSpaceAccountAuth(store, record)in@cotal-ai/workspaceputs that space's account record through aSecretStoreand writes no other key, for persisting a data signing-key rotation or rolling one back. It replaces an existing record only: it refuses when the broker record or the account record is missing, blank or outside the broker's chain, and when the replacement is another account, was issued by another operator, or holds a signing seed its claim does not trust. A record equal to the stored one is not written again, and after a write the record is read back. It is not atomic across keys, so the host must keep other writers of the space's trust records out for the call.validateSpaceAccountAuth(broker, record, space?)in@cotal-ai/coreis the check it uses: the account checks ofvalidateSpaceAuthfor any space on a broker, wherevalidateSpaceAuthaccepts only the space the operator is named for. -
Keep a running command's release identity tied to the code it loaded during staged updates.
Publishing a new canonical package manifest no longer makes an older bootstrapped CLI report or reconcile as the new release. Embedded API calls retain their entry package's version and provenance.
What's Changed
- feat(workspace): replace one space's account record without writing the broker record by @davidfarah2003 in #6831
- test(cli): count the three config-mode checks in the seed total by @davidfarah2003 in #6828
- feat(cli): select verified retained execution generations at startup by @davidfarah2003 in #6812
- fix(update): keep the Windows service running after a manual update by @davidfarah2003 in #6832
- docs(upgrade): explain how to repair an update paused by 0.164.0 through 0.164.8 by @davidfarah2003 in #6834
- fix(desktop): name a stopped background service in Details by @davidfarah2003 in #6830
- test(upgrade): read native macOS socket and launchd states in the upgrade matrix by @davidfarah2003 in #6835
- chore(release): version packages by @davidfarah2003 in #6833
Full Changelog: v0.164.9...v0.164.10