What's New
Engram now has a safe recovery path when MCP write tools start from an ambiguous parent directory with multiple repositories. Agents can recover only after asking the user to choose one of the reported projects.
Changes
Bug Fixes
- Ambiguous project writes:
mem_saveandmem_save_promptcan now retry afterambiguous_projectwith an explicit user-selected project. - Strict project validation: recovery accepts only an exact
available_projectsmatch after trimming whitespace, preventing normalized collisions likefoo-barmatchingfoo--bar. - Correct project metadata: successful recovery reports
project_source: user_selected_after_ambiguous_projectand resolvesproject_pathto the selected repo root when possible. - Clearer errors: empty or invented project choices now return actionable
invalid_project_choiceresponses.
Documentation
- Agent setup flow: documented the full ambiguous-project rescue flow with example error, retry payload, success envelope, and guardrails.
Upgrade
brew upgrade engram