Skip to content

v0.160.0

Choose a tag to compare

@davidfarah-dev davidfarah-dev released this 11 Nov 13:32
3e0a129

macOS: the DMG installers on this page do not start on macOS 26. Use the installers from v0.160.5 or later.

Install or update: npm i -g cotal-ai@0.160.0

Restart running Cotal processes and agent sessions to use the new code.

What changed

  • cotal up --account-resolver full starts the broker on nats-server's full account resolver, so a host can add and retire space accounts on the running broker with pushAccountClaim instead of rendering the configuration again and reloading.
  • cotal --version prints an update line only when a newer version is known or an update needs repair.
  • Updating from a version before 0.159.1 on a computer that hosts a Manager no longer fails its first run at the continuity check.
  • The terminal app can keep which direct messages you read, so an unread one stays listed after a restart and a read one stays gone.
  • Clarify helper spawning and persona channel permissions in the tool descriptions.
Every change in full
  • cotal up --account-resolver full starts the broker on nats-server's full account resolver, so a host can add and retire space accounts on the running broker with pushAccountClaim instead of rendering the configuration again and reloading. up renders the resolver on <root>/.cotal/account-jwts, created owner-private, with deletion off, and records the choice in .cotal/broker-policy.json, so a later cotal up on the root renders it again without the flag. --account-resolver memory on a stopped root takes the record back. A running broker refuses a different value, because nats-server switches resolvers only at start, and --open, -f and --restore refuse the flag. A renderer outside up passes brokerAccountResolver(root, readBrokerPolicy(root)?.accountResolver) from @cotal-ai/workspace, so its render names the same directory and limit. Before, up always rendered resolver: MEMORY, so a broker it started could never take a pushed account, and a host that rendered the full resolver had its next reload refused.

  • cotal --version prints an update line only when a newer version is known or an update needs repair. It no longer prints "update status unknown" or "up to date" under the version.

  • Updating from a version before 0.159.1 on a computer that hosts a Manager no longer fails its first run at the continuity check. The update waits for the restarted daemon before it checks, as it did before 0.159.1.

  • The terminal app can keep which direct messages you read, so an unread one stays listed after a restart and a read one stays gone.

    readMarks() and markRead() from @cotal-ai/workspace/chat read and record message ids in a private read.json beside a space's remembered chat sessions, which keeps the newest 1000 and takes a lock for each write. forgetChatSessions(), and so cotal space forget, removes it with the sessions.

  • Clarify helper spawning and persona channel permissions in the tool descriptions.
    Shorten the grants guidance, describe delegated capabilities without a fixed list, remove the harness list from the single-job guidance, and explain channel wildcards in saved personas.

What's Changed

  • feat(tui): list unread direct messages in the inspector by @Manas-Kenge in #6352
  • fix(connector-core): clarify spawn and persona guidance by @davidfarah2003 in #6358
  • feat(cli): start the broker on the full account resolver with up --account-resolver by @davidfarah2003 in #6359
  • fix(update): wait for the restarted daemon before continuity when the parent wrote no journal by @davidfarah2003 in #6360
  • fix(cli): print an update line under the version only when there is one to act on by @davidfarah2003 in #6361
  • chore(release): version packages by @davidfarah2003 in #6357

Full Changelog: v0.159.1...v0.160.0