feat(client): enforce pack memory requirements at activation#20
Merged
Conversation
Project config.toml gains an optional [memory] adapter declaration. Client::activate now refuses a persona whose manifest declares memory_required = "hard" when the project declares no adapter, with an error naming the config file to edit. Soft requirements surface as warnings from the CLI activate/use commands and as a memory_warning field in the MCP activate response. The sync client only checks the declaration; live connectivity checks stay with the async surfaces.
Ghost-Frame
force-pushed
the
feat/memory-requirement-enforcement
branch
from
July 6, 2026 16:45
d2a5364 to
1c7179e
Compare
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
1 participant
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.
Closes the gap where
memory_requiredwas declared in pack manifests and enforced byRuntime::check_memory_capability, but no live loader ever checked it.[memory]adapter declaration (adapter,endpoint,path), serde-defaulted so existing configs parse unchanged.Client::activaterefuses a persona whose manifest declaresmemory_required = "hard"when the project declares no adapter; the error names the exact config file to edit.frameshift activate/use, and amemory_warningfield in the MCP activate response.memory_requirement_statushelper exposes requirement + declaration state.MemoryAdapter.🤖 Generated with Claude Code