Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

Create a Memory Store changedapi/beta/memory_stores/create

Nearest release: v2.1.306, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+26added
Lines−12removed
From line 1 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits18to this page, all time

# Create a Memory Store # Create a memory store

The whole hunk

from line 1, old and new numbered
/
lines
from line 1
11---
2title: Create a memory store
2title: Create a Memory Store
33url: https://platform.claude.com/docs/en/api/beta/memory_stores/create
44---
55 
6# Create a memory store
6# Create a Memory Store
77 
88**POST** `/v1/memory_stores`
99 
10Create a memory store
10Create a Memory Store
1111 
1212## Headers
1313 
from line 135
135135 
136136- `name: string`
137137 
138 Human-readable name for the store. Required; 1–255 characters; no control characters. The mount-path slug under `/mnt/memory/` is derived from this name (lowercased, non-alphanumeric runs collapsed to a hyphen). Names need not be unique within a workspace.
138 The name of the memory store, 1 to 255 characters long, without control characters. Names don't have to be unique in a workspace.
139139 
140 In a session, the store's directory under `/mnt/memory/` is based on this name. The name is lowercased and every run of characters other than ASCII letters and digits becomes one hyphen. The session's memory store resource gives the exact path in `mount_path`.
141 
142 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#how-the-agent-accesses-memory) to learn more about how agents access memory stores.
143 
140144 minLength: 1, maxLength: 255
141145 
142146- `description: optional string`
143147 
144 Free-text description of what the store contains, up to 1024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent.
148 Free-text description of what the store contains, up to 1,024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent.
145149 
146150 maxLength: 1024
147151 
148152- `metadata: optional map[string]`
149153 
150 Arbitrary key-value tags for your own bookkeeping (such as the end user a store belongs to). Up to 16 pairs; keys 1–64 characters; values up to 512 characters. Not visible to the agent.
154 Key-value pairs for your own use, such as the end user that the store belongs to. The agent doesn't see them.
151155 
156 A store has at most 16 pairs. Keys are 1 to 64 characters long and values at most 512 characters.
157 
152158## Returns
153159 
154160- `BetaManagedAgentsMemoryStore object`
from line 165
159165 
160166 - `id: string`
161167 
162 Unique identifier for the memory store (a `memstore_...` tagged ID). Use this when attaching the store to a session, or in the `{memory_store_id}` path parameter of subsequent calls.
168 The unique ID of the memory store (`memstore_...`). Use it to attach the store to a session.
163169 
164170 - `archived_at: string or null`
165171 
166 Timestamp when the store was archived, or `null` if active. Set once and never cleared; archiving is one-way. Archived stores are read-only and cannot be attached to new sessions.
172 When the memory store was archived, in RFC 3339, or `null` if it hasn't been.
167173 
174 Archiving can't be undone. An archived store can't be attached to new sessions. You can't create or update its memories or update the store. You can still read and delete its memories, redact their versions, and delete the store.
175 
176 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#archive-a-store) to learn more about archiving.
177 
168178 format: date-time
169179 
170180 - `created_at: string`
171181 
172 Timestamp when the store was created.
182 When the memory store was created, in RFC 3339.
173183 
174184 format: date-time
175185 
176186 - `description: string`
177187 
178 Free-text description of what the store contains, up to 1024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.
188 Free-text description of what the store contains, up to 1,024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.
179189 
180190 - `metadata: map[string]`
181191 
182 Arbitrary key-value tags for your own bookkeeping (such as the end user a store belongs to). Up to 16 pairs; keys 1–64 characters; values up to 512 characters. Returned on retrieve/list but not filterable.
192 Key-value pairs for your own use, such as the end user that the store belongs to.
183193 
194 A store has at most 16 pairs. Keys are 1 to 64 characters long and values at most 512 characters. You can't filter lists by metadata.
195 
184196 - `name: string`
185197 
186198 Human-readable name for the store. 1–255 characters. The store's mount-path slug under `/mnt/memory/` is derived from this name.
from line 199
187199 
188200 - `updated_at: string`
189201 
190 Timestamp when the store's `name`, `description`, or `metadata` was last modified. Memory writes inside the store do not advance this.
202 When the memory store was last changed, in RFC 3339.
203 
204 Changing its `name`, `description`, or `metadata` updates it. Archiving the store does too. Changes to the store's memories don't.
191205 
192206 format: date-time
193207 
Feedback