v0.11.1 — dynamic tool guide and memory store caps#20
Merged
Conversation
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.
Summary
Tool guideblock in the system prompt. Rendered from the same profile-filtered definitions offered to the model, so it cannot drift from the actual toolset; optional tools (memory_*,web_*,skill_read) appear only when registered, andupdate_planappears only while a plan is active or blocked, preserving the proposal-vs-execution split. ~82 tokens for the default toolset.memory.json(global and project separately) is capped at 1800 serialized characters. Writes that would exceed the cap are rejected with a clear instruction to forget or compact first. The cap ratchets against the normalized current payload size, so legacy over-cap stores can always shrink (forget keeps working) while growth stays rejected until the store complies./memory compact: replacements are preflighted for every store before any file is written — a rejected optimization can no longer partially mutate global memory while leaving project memory untouched.memory_propose_updatedocuments the global-vs-project scope policy in its tool description./memory add,/memory forget, and/memory compact.Testing
Docs
DESIGN.md updated in the same commit: ContextAssembler block order (tool guide), §16 memory cap + ratchet + atomic compact, §19 prompt rationale (PROMPT_VERSION 6).