Skip to content

reply-tracking: rename size budgets to maxEntriesPerChat / maxBytesPerChat - #1363

Merged
yagop merged 1 commit into
masterfrom
refactor/reply-tracking-perchat-names
Sep 7, 2026
Merged

yagop merged 1 commit into
masterfrom
refactor/reply-tracking-perchat-names

Conversation

@yagop

@yagop yagop commented Sep 7, 2026

Copy link
Copy Markdown
Owner

replyTracking.maxEntries / maxBytes didn't convey scope: each budget bounds one session key's reply tables (per chat with the default getSessionKey), not a global total. Rename to maxEntriesPerChat / maxBytesPerChat.

createSession({ store, replyTracking: { maxEntriesPerChat: 50, maxBytesPerChat: 8192 } });

defaultTtlSeconds / slidingTtl are per-marker time semantics and keep their names.

Breaking rename within the 2.2.0 prerelease line — the old names shipped only in 2.2.0-rc1 (under the next dist-tag), so no stable release is affected. Source, example, tests, README and CHANGELOG updated; doc/api.md regenerated. npm run check clean (248 tests).

🤖 Generated with Claude Code

…rChat

The bare `maxEntries` / `maxBytes` did not convey that each budget bounds one
session key's tables (per chat with the default getSessionKey), not a global
total. Rename them to `maxEntriesPerChat` / `maxBytesPerChat`.

Breaking rename within the 2.2.0 prerelease line - the old names shipped only in
2.2.0-rc1 (under the `next` dist-tag). Docs, example, tests, and CHANGELOG
updated; doc/api.md regenerated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@yagop
yagop merged commit bf508c2 into master Sep 7, 2026
8 checks passed
@yagop yagop mentioned this pull request Sep 7, 2026
3 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant