Skip to content

v4.10.2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@kevintseng kevintseng released this 21 Sep 19:15
v4.10.2
59863e9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This is a trial release on the npm next tag. latest stays at 4.9.4 until the trial has been observed for at least one working day.

npm install -g @pcircle/memesh@next

4.10.2 includes everything in 4.10.1 (also a trial release) and the fixes listed here.

New

  • A Claude Code session can now be told that a message is waiting for it. Start the session with MEMESH_RECIPIENT=<its recipient id> and it is reminded at the start and at every prompt, until it records the intake action for those messages. Without the variable nothing changes.
  • A briefing setting with three levels for how much MeMesh puts into a new session: minimal, standard (the new default) and full (what earlier versions did). Set it with memesh config set briefing <level>.

Changed

  • The default session briefing is smaller. It now leaves out the parts the host already carries itself and injects this project's own recent memory and the live repository state. memesh config set briefing full brings the old behaviour back.
  • import no longer brings back a memory you archived (#363).

Fixed

  • Imported bundles can no longer grant themselves behavioural authority (#359, #361): fields that change how MeMesh behaves (guards, the demo marker, task state and similar) are refused, or accepted only after validation.
  • Pre-edit recall no longer injects unrelated memories or session bookkeeping in place of what is relevant to the file being edited (#358).
  • The prompt reminder hook works when MeMesh is installed under a symlinked path (#372); before, it exited having done nothing.
  • A guard warning is no longer lost to a slow lock: the counter that tallies guard fires now waits at most 200 ms for the database (#366).
  • A failed memory read is reported as a failure, not as an empty project, and an unreadable message inbox is recorded instead of looking like a clean run (#386, #394).
  • Stale task state (older than 72 hours, or of unknown age) is flagged instead of being presented as current.

For contributors

  • The tests with tight time limits that failed at random on slow Windows runners have generous limits now.

Full detail: CHANGELOG.md.

Assets 2
Loading