Repository navigation
Bump the agent-memory group with 2 updates - #7
Open
Conversation
Bumps AgentMemory from 1.5.0 to 2.3.0 Bumps AgentMemory.AgentFramework from 1.5.0 to 2.3.0 --- updated-dependencies: - dependency-name: AgentMemory dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: agent-memory - dependency-name: AgentMemory.AgentFramework dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: agent-memory ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
This branch had an error being deployed
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.
Updated AgentMemory from 1.5.0 to 2.3.0.
Release notes
Sourced from AgentMemory's releases.
2.3.0
The Pablo Piovano release 2: a fix and some improvements
2.2.0, the Pablo Piovano release, was out for a day. Here is the story so far, and why 2.3.0 follows so soon.
Pablo's experiment gave three months of Bruna's chat to a notes file, a vector store and AgentMemory, then asked three
questions. Its first finding, that recall never looked at the calendar, was fixed in 2.1.0. Running it again found a
second, quieter problem: AgentMemory decided identity by name, so two different colleagues called Alex Kim became one,
silently and for good, and events weren't recorded at all. 2.2.0 fixed that with evidence-based identity.
2.2.0 also listed its own limits. Recall still found people by similarity, export and import carried the current state
but not identity's history, and hosts running GLM-5.3-Flash through
AgentMemory.Inferenceran it at maximum reasoningeffort. Those were meant for 2.2 and missed it. 2.3.0 brings all three.
Checking the release found two critical bugs as well, both in how the database schema reaches an application, and a
review of this release found a third, in 2.2.0 too, in owner import. All three are fixed here. If you run 2.2.0,
upgrade.
Thank you again, Pablo. Your scenario is now the benchmark every identity change is measured against, this release
included (three-memories-one-question, MIT).
Before it shipped, this release went through three Copilot reviews and five independent review rounds; every finding
was fixed with a test that failed first, or is listed under known limits below.
Three critical fixes
AgentMemorypackage. 2.2.0 copied them next toan application that references
AgentMemory.Neo4jdirectly, but NuGet doesn't pass a dependency's files on, so theREADME's install path got none of the 18 scripts. They now ship inside the library, and the release pipeline installs
the package into a clean application and fails unless all of them are there.
ISchemaBootstrapper.BootstrapAsync(), whichcreated the base indexes itself but never ran the scripts; only this repository's command-line tool and tests did. So
identity, on by default since 2.2.0, has run without its unique constraints and lookup indexes: two writes at the same
moment could duplicate an identity record, and lookups slow down as a store grows. Bootstrap now applies the scripts,
each once per database.
could link imported memories to another owner's entities, or create bare nodes. Import now links only to the
entities it brings and to shared ones the store holds; a link to anything else (another owner's entity, a missing one,
or an id that isn't an entity) is left out and counted, the same either way. It writes only what each record's schema
declares, always for the importing owner. Source message ids that aren't the importing owner's own messages become
markers, so recall never quotes another owner's messages from an imported fact, and no message can be written at a
marker's id later.
Also fixed
and review failed when that was no longer one of the decision's own.
... (truncated)
2.2.0
Memory that knows who is who: the Pablo Piovano release
Pablo's experiment gave three months of Bruna's chat to a notes file, a vector store and AgentMemory, then asked three
questions. Its first finding, that recall never looked at the calendar, was fixed in 2.1.0.
Running his scenario again found a second, quieter problem. To decide whether a mention is something already stored,
AgentMemory matched names. A matching name meant the same entity: right most of the time, and wrong, silently and for
good, when two people share a name. In my tests two different colleagues called Alex Kim became one. Events weren't
recorded at all, so Bruna's go-live in September and "the cutover" in November could never be followed as one thing.
None of this raised an error. The answers just got quietly worse.
Thank you, Pablo, for building the test I should have written myself, for publishing everything it produced,
and for letting me run it again (three-memories-one-question,
MIT). Both of the things it found are fixed, and this release carries your name.
What's new
UseMemoryWriter).model (
AddIdentityAdjudicationgives it a dedicated model instead).(
ListPendingAsync,ReviewAsync,GetHistoryAsync).RecallOptions.EventDetails).identity: evidence-based, oridentity: previous resolver (the store-aware writer is off; it can merge different things that share a name).joins imported entities to what the destination already holds.
Measured
Pablo's scenario is now a standing benchmark: the previous resolver against evidence-based identity, the same model
(GLM-5.3-Flash), two runs for every change.
Details and limits:
docs/evidence-based-identity-evaluation-results.md.... (truncated)
2.1.0
Memory that looks at the calendar
Pablo gave three months of one person's chat to a notes file, a vector store and AgentMemory 1.9.0. Then he asked three
questions. Bruna's go-live is on Friday 11 December in Córdoba, and in November she had mentioned her sister's wedding in
Bariloche, where she'd be from the 9th to the 13th. When she asked "plan my prep for go-live week", all three memories
missed the clash, and none of them said so.
The graph had stored the go-live's date. But recall chose facts by how much their words resemble the question, and a trip
to Bariloche resembles nothing in "plan my prep". 2.1.0 adds recall that reads by date.
Thank you, Pablo, for the experiment, for publishing every prompt it produced, and for letting us bring your scenario
into this repository (three-memories-one-question, MIT).
What's new
filter them.
RecallOptions.Upcoming: for a question that looks ahead, the facts that start in the next 14 days.RecallOptions.TimeWindows: the facts dated inside a period the question names ("between December 7 and 13", "nextweek") or anchors on an event ("go-live week" → the Monday-to-Sunday week of the go-live).
RecallOptions.OverlapExpansion: the facts that overlap in time with the dated facts recalled.LlmExtractionOptions.DatesFromTextreads the dates a store-aware writer fact states("on Friday, December 11", "from December 9 to December 13") into its date fields as well. The words stay as written.
It's deterministic and makes no model call.
AgentMemoryPresets.Choose(configuration)readsAgentMemory:Preset, with Recommended when it's absent.tools/AgentMemory.Scenarios. Scripted scenarios, live and fully traced: every model call, span and log line.the right date.
Also fixed
An operation whose quote isn't in the message isn't stored, and a found quote keeps its offsets in the memory's
metadata. On Bruna's history, 166 of 166 quotes were found exactly.
reason code, on the write span and in the debug log.
with the same text stay two results.
live entities match a name at the same rank, a fact or edge isn't attached to either: before, the more-mentioned one
got it.
... (truncated)
2.0.0
Most agent memory asks you to take it on faith: plug it in, hope it helps, find out in production. 2.0.0 is built on the
opposite idea. A memory component earns its place. It is verified, walked within declared budgets, trialled on the
host's own work, and switched on only if it measurably helps. Then the decision is signed, kept, and revocable.
That idea now has a format, a procedure, three independent readers and a preprint behind it.
The preprint lives on Zenodo at that DOI. This release is its code and evidence: the tag
v2.0.0is the exact sourcesnapshot, and the evidence bundle below holds every signed decision the paper reports, with the means to check it.
The three big things
1. Memory packs (ampack). A pack is a signed bundle of memory a host can verify byte for byte: a canonical file list
gives every pack one SHA-256 identity, signatures are checked against the receiver's own trust policy, and declared
relations tell the host how to walk it, within budgets the host sets. Then comes the part nobody else does: the pack is
installed switched off, trialled against the host's own retrieval on the host's own history, and switched on only if it
meets its targets. The decision is a signed in-toto statement bound to the exact content. Readers in .NET, Python and Rust
agree on every one of 514 conformance vectors.
2. A memory that writes better and recalls smarter (the Recommended preset). One opt-in line,
MemoryOptions.CreateRecommended(), switches on what our storage and retrieval research measured as better:The judge is a blend of two models behind the System One protocol; if one is down the other carries on, and if neither
answers, recall falls back to the similarity floor and says so. Low-level and Conversational defaults stay compatible:
nothing changes unless you choose Recommended.
3. A trust boundary on every MCP surface. Recalled memory can hold text someone else wrote. Every MCP tool and
resource that returns memory now marks each item with its
trustLeveland aninstructionLikeflag, escapes it so itcannot forge a tag in the client's prompt, tells the client it is data and never instructions, and can withhold
instruction-like text from untrusted sources (
RecallSecurityMode = Strict). One shared detector serves the in-processadapters, the MCP server and the NAMS MCP server.
Also in 2.0.0
floors and signed activation, in this source release; its NuGet preview packages follow on their own preview tag.
walked from the files and symbols a coding agent is touching.
I live in March?" still has an answer.
... (truncated)
1.9.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.8.0...v1.9.0
1.8.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.7.0...v1.8.0
1.7.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.6.1...v1.7.0
1.6.1
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.6.0...v1.6.1
1.6.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.5.0...v1.6.0
Commits viewable in compare view.
Updated AgentMemory.AgentFramework from 1.5.0 to 2.3.0.
Release notes
Sourced from AgentMemory.AgentFramework's releases.
2.3.0
The Pablo Piovano release 2: a fix and some improvements
2.2.0, the Pablo Piovano release, was out for a day. Here is the story so far, and why 2.3.0 follows so soon.
Pablo's experiment gave three months of Bruna's chat to a notes file, a vector store and AgentMemory, then asked three
questions. Its first finding, that recall never looked at the calendar, was fixed in 2.1.0. Running it again found a
second, quieter problem: AgentMemory decided identity by name, so two different colleagues called Alex Kim became one,
silently and for good, and events weren't recorded at all. 2.2.0 fixed that with evidence-based identity.
2.2.0 also listed its own limits. Recall still found people by similarity, export and import carried the current state
but not identity's history, and hosts running GLM-5.3-Flash through
AgentMemory.Inferenceran it at maximum reasoningeffort. Those were meant for 2.2 and missed it. 2.3.0 brings all three.
Checking the release found two critical bugs as well, both in how the database schema reaches an application, and a
review of this release found a third, in 2.2.0 too, in owner import. All three are fixed here. If you run 2.2.0,
upgrade.
Thank you again, Pablo. Your scenario is now the benchmark every identity change is measured against, this release
included (three-memories-one-question, MIT).
Before it shipped, this release went through three Copilot reviews and five independent review rounds; every finding
was fixed with a test that failed first, or is listed under known limits below.
Three critical fixes
AgentMemorypackage. 2.2.0 copied them next toan application that references
AgentMemory.Neo4jdirectly, but NuGet doesn't pass a dependency's files on, so theREADME's install path got none of the 18 scripts. They now ship inside the library, and the release pipeline installs
the package into a clean application and fails unless all of them are there.
ISchemaBootstrapper.BootstrapAsync(), whichcreated the base indexes itself but never ran the scripts; only this repository's command-line tool and tests did. So
identity, on by default since 2.2.0, has run without its unique constraints and lookup indexes: two writes at the same
moment could duplicate an identity record, and lookups slow down as a store grows. Bootstrap now applies the scripts,
each once per database.
could link imported memories to another owner's entities, or create bare nodes. Import now links only to the
entities it brings and to shared ones the store holds; a link to anything else (another owner's entity, a missing one,
or an id that isn't an entity) is left out and counted, the same either way. It writes only what each record's schema
declares, always for the importing owner. Source message ids that aren't the importing owner's own messages become
markers, so recall never quotes another owner's messages from an imported fact, and no message can be written at a
marker's id later.
Also fixed
and review failed when that was no longer one of the decision's own.
... (truncated)
2.2.0
Memory that knows who is who: the Pablo Piovano release
Pablo's experiment gave three months of Bruna's chat to a notes file, a vector store and AgentMemory, then asked three
questions. Its first finding, that recall never looked at the calendar, was fixed in 2.1.0.
Running his scenario again found a second, quieter problem. To decide whether a mention is something already stored,
AgentMemory matched names. A matching name meant the same entity: right most of the time, and wrong, silently and for
good, when two people share a name. In my tests two different colleagues called Alex Kim became one. Events weren't
recorded at all, so Bruna's go-live in September and "the cutover" in November could never be followed as one thing.
None of this raised an error. The answers just got quietly worse.
Thank you, Pablo, for building the test I should have written myself, for publishing everything it produced,
and for letting me run it again (three-memories-one-question,
MIT). Both of the things it found are fixed, and this release carries your name.
What's new
UseMemoryWriter).model (
AddIdentityAdjudicationgives it a dedicated model instead).(
ListPendingAsync,ReviewAsync,GetHistoryAsync).RecallOptions.EventDetails).identity: evidence-based, oridentity: previous resolver (the store-aware writer is off; it can merge different things that share a name).joins imported entities to what the destination already holds.
Measured
Pablo's scenario is now a standing benchmark: the previous resolver against evidence-based identity, the same model
(GLM-5.3-Flash), two runs for every change.
Details and limits:
docs/evidence-based-identity-evaluation-results.md.... (truncated)
2.1.0
Memory that looks at the calendar
Pablo gave three months of one person's chat to a notes file, a vector store and AgentMemory 1.9.0. Then he asked three
questions. Bruna's go-live is on Friday 11 December in Córdoba, and in November she had mentioned her sister's wedding in
Bariloche, where she'd be from the 9th to the 13th. When she asked "plan my prep for go-live week", all three memories
missed the clash, and none of them said so.
The graph had stored the go-live's date. But recall chose facts by how much their words resemble the question, and a trip
to Bariloche resembles nothing in "plan my prep". 2.1.0 adds recall that reads by date.
Thank you, Pablo, for the experiment, for publishing every prompt it produced, and for letting us bring your scenario
into this repository (three-memories-one-question, MIT).
What's new
filter them.
RecallOptions.Upcoming: for a question that looks ahead, the facts that start in the next 14 days.RecallOptions.TimeWindows: the facts dated inside a period the question names ("between December 7 and 13", "nextweek") or anchors on an event ("go-live week" → the Monday-to-Sunday week of the go-live).
RecallOptions.OverlapExpansion: the facts that overlap in time with the dated facts recalled.LlmExtractionOptions.DatesFromTextreads the dates a store-aware writer fact states("on Friday, December 11", "from December 9 to December 13") into its date fields as well. The words stay as written.
It's deterministic and makes no model call.
AgentMemoryPresets.Choose(configuration)readsAgentMemory:Preset, with Recommended when it's absent.tools/AgentMemory.Scenarios. Scripted scenarios, live and fully traced: every model call, span and log line.the right date.
Also fixed
An operation whose quote isn't in the message isn't stored, and a found quote keeps its offsets in the memory's
metadata. On Bruna's history, 166 of 166 quotes were found exactly.
reason code, on the write span and in the debug log.
with the same text stay two results.
live entities match a name at the same rank, a fact or edge isn't attached to either: before, the more-mentioned one
got it.
... (truncated)
2.0.0
Most agent memory asks you to take it on faith: plug it in, hope it helps, find out in production. 2.0.0 is built on the
opposite idea. A memory component earns its place. It is verified, walked within declared budgets, trialled on the
host's own work, and switched on only if it measurably helps. Then the decision is signed, kept, and revocable.
That idea now has a format, a procedure, three independent readers and a preprint behind it.
The preprint lives on Zenodo at that DOI. This release is its code and evidence: the tag
v2.0.0is the exact sourcesnapshot, and the evidence bundle below holds every signed decision the paper reports, with the means to check it.
The three big things
1. Memory packs (ampack). A pack is a signed bundle of memory a host can verify byte for byte: a canonical file list
gives every pack one SHA-256 identity, signatures are checked against the receiver's own trust policy, and declared
relations tell the host how to walk it, within budgets the host sets. Then comes the part nobody else does: the pack is
installed switched off, trialled against the host's own retrieval on the host's own history, and switched on only if it
meets its targets. The decision is a signed in-toto statement bound to the exact content. Readers in .NET, Python and Rust
agree on every one of 514 conformance vectors.
2. A memory that writes better and recalls smarter (the Recommended preset). One opt-in line,
MemoryOptions.CreateRecommended(), switches on what our storage and retrieval research measured as better:The judge is a blend of two models behind the System One protocol; if one is down the other carries on, and if neither
answers, recall falls back to the similarity floor and says so. Low-level and Conversational defaults stay compatible:
nothing changes unless you choose Recommended.
3. A trust boundary on every MCP surface. Recalled memory can hold text someone else wrote. Every MCP tool and
resource that returns memory now marks each item with its
trustLeveland aninstructionLikeflag, escapes it so itcannot forge a tag in the client's prompt, tells the client it is data and never instructions, and can withhold
instruction-like text from untrusted sources (
RecallSecurityMode = Strict). One shared detector serves the in-processadapters, the MCP server and the NAMS MCP server.
Also in 2.0.0
floors and signed activation, in this source release; its NuGet preview packages follow on their own preview tag.
walked from the files and symbols a coding agent is touching.
I live in March?" still has an answer.
... (truncated)
1.9.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.8.0...v1.9.0
1.8.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.7.0...v1.8.0
1.7.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.6.1...v1.7.0
1.6.1
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.6.0...v1.6.1
1.6.0
What's Changed
Full Changelog: joslat/agent-memory-dotnet@v1.5.0...v1.6.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions