Summary instructions
Free-form instructions that steer how a profile’s summary card reads — shared by every profile in the namespace.GET on the same path. instructions: null means none are set and summaries use the neutral default.
A change applies in the background, not instantly. After you edit the instructions, existing summaries are brought into line over time — a rate-limited sweep converges every profile’s card, dormant ones included — so you don’t need new activity on a profile for it to pick up the change.
Preview a candidate note
A wording that reads well on one profile and badly on the next is a wording nobody notices until it is already live. The preview endpoint runs a candidate note against a profile you know well and hands back how that profile’s summary would read under it — without saving the note, and without touching the stored summary.
The response carries
profile_id and text. text is null when nothing was generated — the same signal GET /summary uses for a profile with no card yet, so a caller that already branches on a null summary needs no second empty case.
A preview is slow. It generates a summary on the spot rather than reading a stored one, so it waits where the summary read is fast — bounded at 120 seconds. Use it for setting instructions up, not for a session’s opening context.
PATCH /settings above. The preview and the apply path compose the same query under the hood, so what you tried is what every summary in the namespace will follow.
Related
- Recalling memories — the summary card these instructions steer
- Isolation — what a namespace is, and how it isolates