What happened
agent-framework-azure-cosmos-memory allows azure-cosmos-agent-memory>=0.2.0b3 with no upper bound. Its CosmosMemoryContextProvider also accepts fact, procedural, and episodic memory types, but before_run() sends all selected types through this call:
await self.memory_client.search_cosmos(
search_terms=query_text,
user_id=user_id,
top_k=self.top_k,
memory_types=[str(t) for t in self.memory_types],
min_confidence=self.min_confidence,
)
That no longer implements the public retrieval contract in Agent Memory Toolkit 0.3.0b2:
search_cosmos() removes episodic from memory_types unless include_episodes=True, so episodes configured on the MAF provider are silently omitted.
- Procedural memory is now an atomic procedure library. The Toolkit's supported projection is
build_procedural_context(user_id, task=...), which selects and compiles active, applicable procedures. The MAF provider never calls it and instead formats generic search results.
Why this matters
A fresh installation can legally resolve Toolkit 0.3.0b2, appear healthy, and still miss configured episodes. Procedural context also bypasses the Toolkit's active/in-scope compilation path.
This is the retrieval counterpart to #7633: the provider's open-ended Toolkit dependency moved past another beta API boundary.
Verified versions
agent-framework-core==1.15.0
agent-framework-azure-cosmos-memory==1.0.0a260813
azure-cosmos-agent-memory==0.3.0b2
The provider code is unchanged on current main as of 2026-08-27.
Expected behavior
The provider and its declared dependency range should agree. For Toolkit 0.3.0b2, the provider should:
- use
include_episodes=True when episodic memory is selected, preserving the single shared fact/episode ranking budget;
- exclude procedural records from generic search; and
- obtain procedural context through
build_procedural_context(user_id, task=query_text).
Alternatively, constrain the Toolkit upper bound until that provider support ships.
Public references
What happened
agent-framework-azure-cosmos-memoryallowsazure-cosmos-agent-memory>=0.2.0b3with no upper bound. ItsCosmosMemoryContextProvideralso acceptsfact,procedural, andepisodicmemory types, butbefore_run()sends all selected types through this call:That no longer implements the public retrieval contract in Agent Memory Toolkit
0.3.0b2:search_cosmos()removesepisodicfrommemory_typesunlessinclude_episodes=True, so episodes configured on the MAF provider are silently omitted.build_procedural_context(user_id, task=...), which selects and compiles active, applicable procedures. The MAF provider never calls it and instead formats generic search results.Why this matters
A fresh installation can legally resolve Toolkit
0.3.0b2, appear healthy, and still miss configured episodes. Procedural context also bypasses the Toolkit's active/in-scope compilation path.This is the retrieval counterpart to #7633: the provider's open-ended Toolkit dependency moved past another beta API boundary.
Verified versions
agent-framework-core==1.15.0agent-framework-azure-cosmos-memory==1.0.0a260813azure-cosmos-agent-memory==0.3.0b2The provider code is unchanged on current
mainas of 2026-08-27.Expected behavior
The provider and its declared dependency range should agree. For Toolkit
0.3.0b2, the provider should:include_episodes=Truewhen episodic memory is selected, preserving the single shared fact/episode ranking budget;build_procedural_context(user_id, task=query_text).Alternatively, constrain the Toolkit upper bound until that provider support ships.
Public references
0.3.0b2release notes: https://github.com/AzureCosmosDB/AgentMemoryToolkit/blob/main/CHANGELOG.md#030b2-2026-08-17