我们添加了 agent-memory-2026-07-22 beta 标头，它改变了列出记忆（GET /v1/memory_stores/{memory_store_id}/memories）的行为：结果以稳定的、服务器定义的顺序返回

我们新增了 agent-memory-2026-07-22 测试版标头，该标头改变了列出记忆（GET /v1/memory_stores/{memory_store_id}/memories）的行为：结果以稳定的、由服务器定义的顺序返回，且 order_by 和 order 参数将被忽略；depth 仅接受 0、1 或省略（其他值将返回 400 错误）；path_prefix 必须以 / 结尾，并匹配完整路径段而非子字符串。未使用该标头发出的页面游标在使用该标头时无效，因此采用该标头时请从第一页重新开始。在记忆存储端点上，agent-memory-2026-07-22 替代了 managed-agents-2026-04-01；同时发送两者将返回 400 错误。2026 年 7 月 22 日，managed-agents-2026-04-01 标头将采用相同的列表行为。请参阅测试版标头。Python（0.116.0）、TypeScript（0.110.0）、Go（1.56.0）、Java（2.48.0）、Ruby（1.55.0）、PHP（0.36.0）、C#（12.35.0）和 CLI（1.16.0）SDK 现在在所有记忆存储调用中发送 agent-memory-2026-07-22 而非 managed-agents-2026-04-01。如果你的代码在记忆存储调用中显式传递了测试版标头，请将 managed-agents-2026-04-01 替换为 agent-memory-2026-07-22，而不是添加第二个值。

We've added the agent-memory-2026-07-22 beta header, which changes how listing memories (GET /v1/memory_stores/{memory_store_id}/memories) behaves: results are returned in a stable, server-defined order and the order_by and order parameters are ignored; depth accepts only 0, 1, or being omitted (other values return a 400 error); and path_prefix must end with / and matches whole path segments instead of a substring. Page cursors issued without the header aren't valid with it, so restart from the first page when you adopt it. On memory store endpoints, agent-memory-2026-07-22 replaces managed-agents-2026-04-01; sending both returns a 400 error. On July 22, 2026, the managed-agents-2026-04-01 header adopts the same list behavior. See Beta headers. The Python (0.116.0), TypeScript (0.110.0), Go (1.56.0), Java (2.48.0), Ruby (1.55.0), PHP (0.36.0), C# (12.35.0), and CLI (1.16.0) SDKs now send agent-memory-2026-07-22 on all memory store calls instead of managed-agents-2026-04-01. If your code passes betas explicitly on memory store calls, replace managed-agents-2026-04-01 with agent-memory-2026-07-22 there rather than adding a second value.