Repository navigation
v0.140.0
Install or update: npm i -g cotal-ai@0.140.0
Changes in this release
-
cotal history limitnow sets the limits of DMs and of the delivery daemon's inbox and stored copies as well as channel posts, and takesnonefor any age or count.--inbox-max-ageand--inbox-per-agentset the inbox and stored copies together, and--dm-max-ageand--dm-per-senderset DMs. A new space keeps 1000 stored copies per agent and every DM, as before, andcotal upand connecting never change a limit. A lower limit shows what it deletes for each agent or DM pair and asks first. With no limit flags the command prints the four streams' limits and changes nothing. Its--jsonresult now lists one entry per stream underresult.streams. Restore brings back the recorded limits of all four streams.The delivery daemon stamps each stored copy with the count it was stored under in a
Cotal-Delivery-Limitheader, and the stored-copies notice compares against that count. A copy without the header counts as 1000.In
@cotal-ai/core, the chat-only limit API is replaced by one that takes the stream.ChatHistoryLimitbecomesHistoryLimit, whoseperSenderis nowperSubject;setChatHistoryLimit,describeChatHistory,chatHistoryLimitProblem,chatHistoryLimitOfandchatHistoryRestoreStagingbecomesetHistoryLimit,describeHistoryLimit,historyLimitProblem,historyLimitOfandhistoryLimitRestoreStaging; andChatHistoryChange,ChatHistoryUpdateUnknownandChatHistoryChangedbecomeHistoryLimitChange,HistoryLimitUpdateUnknownandHistoryLimitChanged.isAcceptedChatHistory,CHAT_HISTORY_MIN_AGE_MSandCHAT_HISTORY_MAX_AGE_MSare removed;historyLimitMinAgeMsandHISTORY_MAX_AGE_MSgive the bounds, andhistoryAgeProblemchecks an age on its own, where 0 is an age below the floor. Thestored-copies-fullevent now carries the stampedlimit. -
The manager now calls core's
managedRetirementOpIddirectly at its eight retirement sites. The privateretireOpIdalias, whose whole body called that function, is gone along with its second copy of the contract. The doc onmanagedRetirementOpIdnow also says the id is 26 hex characters, so it is itself a lifecycle token. No behavior changes. -
The auth package's option types now take the data account as
ServiceKeys["dataAccount"]instead of restating{ pub: string; signingSeed: string }across its consumers, so a change to what the auth service holds of the data account reaches every declaration that receives it. No runtime change.
What's Changed
- refactor(manager): call managedRetirementOpId directly by @davidfarah2003 in #5781
- feat!: history limits for DMs and the delivery streams, and none by @davidfarah2003 in #5767
- refactor(auth): share the data-account projection type by @davidfarah2003 in #5784
- docs: name 0.139.1 as the last release without the wider history limits by @davidfarah2003 in #5783
- chore(release): version packages by @davidfarah2003 in #5782
Full Changelog: v0.139.1...v0.140.0