You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**L2 (`-d`)**: Max 40000 characters. Full content, retrieved on-demand only.
13
13
14
+
**Memory is not immutable; it is accountable.** Wrong write, stale fact, captured a piece of PII you shouldn't have? Use `continuity retract <uri> --reason "..."` to mark it retracted. The memory stays in the tree as a marker but is excluded from default reads. Pass `--superseded-by <new-uri>` when you have a replacement to preserve trajectory. Operators don't run this verb — it exists for the agent to curate its own substrate. The trust contract is what governs the substrate, not architectural enforcement.
15
+
14
16
## What This Is
15
17
16
18
Continuity gives Claude Code (and eventually any AI agent) memory that persists across sessions. It captures what happened, what was learned, and how you work — then injects that context into future sessions so the agent doesn't start cold every time.
--reason "preference changed after 2026-04 review" \
256
+
--superseded-by mem://user/preferences/new-style
257
+
```
258
+
259
+
Retracted memories stay in the tree — nothing is silently erased. Pass `--include-retracted` to `show` or `tree` to inspect them. The reason text is sequestered behind that flag (absent from default responses, not empty or redacted), so confronting your own past retraction is a deliberate act.
260
+
261
+
The verb exists for the agent to curate its own substrate. Operators don't run it. The trust contract is what governs the substrate, not architectural enforcement.
262
+
244
263
## API
245
264
246
265
All endpoints on `http://127.0.0.1:37777`:
247
266
248
267
| Method | Path | Description |
249
268
|--------|------|-------------|
250
269
|`GET`|`/api/health`| Server health + uptime |
251
-
|`GET`|`/api/tree?uri=`| Browse memory tree |
270
+
|`GET`|`/api/tree?uri=&include_retracted=`| Browse memory tree |
271
+
|`GET`|`/api/memories?uri=&include_retracted=`| Fetch a single memory |
272
+
|`POST`|`/api/memories`| Store a memory directly |
273
+
|`POST`|`/api/memories/retract`| Retract a memory (tombstone or supersession) |
- Browsing what you know: `+"`continuity tree [uri]`"+`
28
28
- Understanding who you're working with: `+"`continuity profile`"+`
29
+
- Retracting a memory you wrote: `+"`continuity retract <uri> --reason \"...\"`"+` (or with `+"`--superseded-by`"+` to link a successor)
29
30
30
31
Before searching the codebase for prior decisions, conventions, or context — check continuity first. If you learn something worth keeping, store it immediately.
32
+
33
+
**Memory is not immutable; it is accountable.** When a write you made turns out to be wrong, stale, or sensitive, retract it — the memory is preserved as a marker but excluded from default reads. Retraction is for *you*, the agent: operators don't run this verb. The trust contract is what governs the substrate, not enforcement at the CLI.
rememberCmd.Flags().StringVarP(&rememberDetail, "detail", "d", "", "L2 full content — max 40000 chars (optional)")
47
48
rememberCmd.Flags().StringVar(&rememberSession, "session", "", "Session ID for provenance (optional)")
49
+
rememberCmd.Flags().BoolVar(&rememberAcknowledgeRetracted, "acknowledge-retracted", false, "Proceed past a dedup match against retracted memory (use after inspecting with `show --include-retracted`)")
0 commit comments