Added
Alloy.Memorybehaviour — first-class protocol for Anthropic'smemory_20250818tool. Six callbacks (view,create,str_replace,insert,delete,rename) that any store can implement. Alloy owns the wire format and path validation; your code owns the backing store. Matches the split used by Anthropic's own Python SDK (BetaAbstractMemoryTool).- Anthropic provider memory wiring — passing
memory: {StoreModule, store_opts}toAlloy.run/2injects thememory_20250818tool into the request and adds thecontext-management-2025-06-27beta header. Memory tool calls are routed throughAlloy.Memory.Routerrather than the generic tool executor, keeping the pipelines clean. Alloy.run/2:memoryoption — validates at entry that memory requiresAlloy.Provider.Anthropic(raisesArgumentErrorotherwise). Other providers will be wired as they ship their own memory primitives.- Model catalog — added context-window entries for Kimi K2.5/K2.6 (256K), Gemma 4 family (256K), GLM-4.6 (200K), Qwen 3 family including
qwen3-coder-plusandqwen3.5-397b-a17bat 1M context, Mistral Large 3 (256K). All drop-in through existing providers — no new provider modules.
Non-breaking
Memory is additive surface area. Callers who do not pass :memory see zero behavioural change. The context-management-2025-06-27 beta header is injected only when memory is configured.
Full changelog: https://github.com/alloy-ex/alloy/blob/main/CHANGELOG.md
🤖 Generated with Claude Code