Skip to content

Bump the agent-memory group with 2 updates - #37

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step06_MemoryUsingAgentMemory/agent-memory-78a4e0d0c1
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step06_MemoryUsingAgentMemory/agent-memory-78a4e0d0c1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 15, 2026

Copy link
Copy Markdown
Contributor

Updated AgentMemory from 1.5.0 to 2.1.0.

Release notes

Sourced from AgentMemory's releases.

2.1.0

Memory that looks at the calendar

"Your agent doesn't forget with an error. It forgets with a tidy answer."
— Pablo Piovano, on LinkedIn, 3 November 2026

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

  • Look-ahead recall. Three reads by date, each in its own section with its own budget. The retrieval judge doesn't
    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", "next
      week") 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.
  • Dates read into date fields. LlmExtractionOptions.DatesFromText reads 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.
  • Recommended is the default.
    • AgentMemoryPresets.Choose(configuration) reads AgentMemory:Preset, with Recommended when it's absent.
    • Without a retrieval judge it runs the Conversational preset, and the memory tiers line says why.
    • The Recommended preset now includes look-ahead recall and date reading.
    • Existing registrations and the Conversational preset are unchanged.
  • tools/AgentMemory.Scenarios. Scripted scenarios, live and fully traced: every model call, span and log line.
    • It checks deterministically that each needed fact is in one item of the prompt, and that the store holds it with
      the right date.
    • Answers are logged and never graded.
    • It ships Bruna's go-live, and a busier variant with 81 more ordinary statements.

Also fixed

  • The store-aware writer checks each quote (#​249).
    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.
  • The writer records what it drops (#​250), with a
    reason code, on the write span and in the debug log.
  • Hybrid retrieval fuses by node (#​248), so two nodes
    with the same text stay two results.
  • Ambiguous names resolve to nothing (#​251). When two
    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

Packages: the 2.0.0 packages did not reach NuGet, because the publishing key had expired. Install 2.1.0, which contains everything below plus look-ahead recall. This page keeps the 2.0.0 notes and the evidence behind the preprint.

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.

José Luis Latorre Millas. ampack: signed, declaratively traversable memory packs for AI agents, with trial-gated
activation.
Preprint v0.10, 5 November 2026. doi:10.5281/zenodo.24012989

The preprint lives on Zenodo at that DOI. This release is its code and evidence: the tag v2.0.0 is the exact source
snapshot, 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:

What With Recommended Before
Stored memories that were right (store-aware writer, two fresh worlds) 90.8% and 87.8% 42.3% and 39.1%
Turns where every needed memory reached the prompt (judge at the fan-in) 96.1% and 96.5% 67.6% and 76.8% (similarity floor)
Knowledge-update questions answered (of 78) 72 and 71 63

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 trustLevel and an instructionLike flag, escapes it so it
cannot 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-process
adapters, the MCP server and the NAMS MCP server.

Also in 2.0.0

  • The Extensibility module SDK 0.1.1: composable memory modules with declared traversal, snapshots, confidence
    floors and signed activation, in this source release; its NuGet preview packages follow on their own preview tag.
  • Coding memory (experimental): decisions, repository experience and a code map read from Roslyn or any SCIP index,
    walked from the files and symbols a coding agent is touching.
  • Bitemporal by default in Recommended: a change ends the old value's valid time and keeps it believed, so "where did
    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.1.0.

Release notes

Sourced from AgentMemory.AgentFramework's releases.

2.1.0

Memory that looks at the calendar

"Your agent doesn't forget with an error. It forgets with a tidy answer."
— Pablo Piovano, on LinkedIn, 3 November 2026

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

  • Look-ahead recall. Three reads by date, each in its own section with its own budget. The retrieval judge doesn't
    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", "next
      week") 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.
  • Dates read into date fields. LlmExtractionOptions.DatesFromText reads 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.
  • Recommended is the default.
    • AgentMemoryPresets.Choose(configuration) reads AgentMemory:Preset, with Recommended when it's absent.
    • Without a retrieval judge it runs the Conversational preset, and the memory tiers line says why.
    • The Recommended preset now includes look-ahead recall and date reading.
    • Existing registrations and the Conversational preset are unchanged.
  • tools/AgentMemory.Scenarios. Scripted scenarios, live and fully traced: every model call, span and log line.
    • It checks deterministically that each needed fact is in one item of the prompt, and that the store holds it with
      the right date.
    • Answers are logged and never graded.
    • It ships Bruna's go-live, and a busier variant with 81 more ordinary statements.

Also fixed

  • The store-aware writer checks each quote (#​249).
    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.
  • The writer records what it drops (#​250), with a
    reason code, on the write span and in the debug log.
  • Hybrid retrieval fuses by node (#​248), so two nodes
    with the same text stay two results.
  • Ambiguous names resolve to nothing (#​251). When two
    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

Packages: the 2.0.0 packages did not reach NuGet, because the publishing key had expired. Install 2.1.0, which contains everything below plus look-ahead recall. This page keeps the 2.0.0 notes and the evidence behind the preprint.

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.

José Luis Latorre Millas. ampack: signed, declaratively traversable memory packs for AI agents, with trial-gated
activation.
Preprint v0.10, 5 November 2026. doi:10.5281/zenodo.24012989

The preprint lives on Zenodo at that DOI. This release is its code and evidence: the tag v2.0.0 is the exact source
snapshot, 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:

What With Recommended Before
Stored memories that were right (store-aware writer, two fresh worlds) 90.8% and 87.8% 42.3% and 39.1%
Turns where every needed memory reached the prompt (judge at the fan-in) 96.1% and 96.5% 67.6% and 76.8% (similarity floor)
Knowledge-update questions answered (of 78) 72 and 71 63

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 trustLevel and an instructionLike flag, escapes it so it
cannot 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-process
adapters, the MCP server and the NAMS MCP server.

Also in 2.0.0

  • The Extensibility module SDK 0.1.1: composable memory modules with declared traversal, snapshots, confidence
    floors and signed activation, in this source release; its NuGet preview packages follow on their own preview tag.
  • Coding memory (experimental): decisions, repository experience and a code map read from Roslyn or any SCIP index,
    walked from the files and symbols a coding agent is touching.
  • Bitemporal by default in Recommended: a change ends the old value's valid time and keeps it believed, so "where did
    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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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

Bumps AgentMemory from 1.5.0 to 2.1.0
Bumps AgentMemory.AgentFramework from 1.5.0 to 2.1.0

---
updated-dependencies:
- dependency-name: AgentMemory
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: agent-memory
- dependency-name: AgentMemory.AgentFramework
  dependency-version: 2.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: agent-memory
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 15, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: .NET. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants