Memory that follows you: Palinode v0.13.0 goes cross-harness #128
Paul-Kyle
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
An agent can remember perfectly and still feel forgetful if the memory only appears when you stop and ask for it. Palinode v0.13.0 closes that gap: memory now follows the working turn across more harnesses.
The release adds two native recall paths:
UserPromptSubmithook, installed bypalinode init, that checks prospective triggers and runs a strict-threshold search before each prompt.Both use the same environment knobs. Both inject memory into the conversation rather than rewriting the system prompt, so the provider's prompt-cache prefix remains stable. A new cross-harness guide maps native hooks, native plugins, and MCP integrations in one place.
The default implicit-recall threshold also moves from
0.75to0.5, based on the measured BGE-M3 calibration already carried by Palinode. Injected hits now show the raw cosine score—the same scale the threshold actually controls—so tuning matches what you see.There is a second story in this release that matters just as much: nine inbound PRs from five external contributors shipped in the three days since v0.12.0. Thank you to floze-the-genius, WilliamK112, SkxOverKill, ColumbusLabs, and Tethys0. The contribution pipeline—claim, review, merge, preserve authorship, and carry the work into a release—is working in public, not just described in a contributing guide.
Also shipped: MCP result-size audit fields, a bounded MCP search limit, deterministic bullet-list migration, relative-date lint findings, safer injection scanning, and a fix for oversized API searches crossing sqlite-vec's KNN ceiling.
Read the full notes and contributor credits in v0.13.0 — Memory that follows you.
All reactions