Repository navigation
build: develop and test against core 0.0.33; fix version notes in the README - #33
Merged
Merged
Conversation
… README - devDependency (root and demo) ^0.0.30 -> ^0.0.33. On 0.0.x a caret pins the patch, so CI and the e2e were running against 0.0.30, not the core users get. Lockfiles: only the core's entries changed. - README: the peer floor sentence said >=0.0.20; it is >=0.0.30 (first core with the learning notebook). agent.usage / agent.sessionUsage() need >=0.0.32. - demo: the compaction threshold was a fixed 6000 tokens, under what the fixed prompt, tool definitions and skills weigh since core 0.0.32 - it would compact on every run. Now min(24000, 85% of the window). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur
The explicit thresholdTokens was a leftover of the old core's estimate. It is removed, as agreed: the core compacts at 85% of the window, judged on the whole context. /compact and the context meter's button show compaction sooner. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur
siarheidudko
marked this pull request as ready for review
November 9, 2026 09:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
@dudko.dev/agent-webis a peer dependency (so a host app shares one core instance) and also a dev dependency (so this repo can build and test). On0.0.xa caret pins the patch:^0.0.30is exactly 0.0.30, so CI and the e2e were running against 0.0.30 while users get 0.0.33.What
^0.0.30→^0.0.33. The lockfiles change only the core's entries (a plainnpm installalso stripped unrelatedlibcmetadata with this npm; reverted).agent.usage/agent.sessionUsage()need core>=0.0.32(the peer range allows>=0.0.30). The peer-floor sentence said>=0.0.20; the real floor is>=0.0.30(the first core with the learning notebook — checked against the published 0.0.29 / 0.0.30 / 0.0.31 packages).thresholdTokens(6000) is removed. It was a leftover of the old core's estimate; since core 0.0.32 the fixed prompt, tool definitions and skills count towards the threshold, so 6000 would compact on every run. The core's 85% default applies now;/compactand the context meter's button show compaction sooner.>=0.0.30.Checks
typecheck,format:check,build,test(70 pass), demotypecheck+build, and the Playwright e2e (22 pass) — all against core 0.0.33.🤖 Generated with Claude Code
https://claude.ai/code/session_011FKop4At26QqqkwVGEjJur