Document memory blocks in mixin kits#25094
Merged
Merged
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The kits doc described `memory:` only as part of agent kits, but mixin kits also support it. When several kits with memory load together, each kit's content lands in its own `kits-memory/<kit>.md` file and the main memory file gets a `## Kits` index pointing to them — a layout that lets the agent lazy-read kit-specific guidance instead of carrying every kit's memory on every turn. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ac8edc2 to
e256af0
Compare
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The added documentation is clear, accurate, and well-structured. The new memory: sections correctly describe both the mixin and agent kit behavior, the split-file layout under kits-memory/, and the <!-- sbx:kits-section start/end --> markers. No hedge words, marketing language, or style violations were found. Scope matches the existing document's character.
aevesdocker
approved these changes
May 19, 2026
mdelapenya
approved these changes
May 19, 2026
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
The kits doc described the
memory:field only under agent kits, but mixin kits also support it. When several loaded kits each declare amemory:block, the content is split across per-kit files under a siblingkits-memory/directory and the main memory file gets a## Kitsindex pointing to them — a layout that lets the agent lazy-read kit-specific guidance instead of carrying every kit's memory in context on every turn.This PR:
memoryto the intro capability listInject agent memorysubsection under "What kits can do" (memory applies to both mixin and agent kits)kits-memory/<kit>.mdsplit-file pattern with the<!-- sbx:kits-section start/end -->markersGenerated by Claude Code