Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(web): state that the page listings leave out expired pages

Vinícius DS Andrade4d83f7b9258b
diff --git a/docs/frontend-api.md b/docs/frontend-api.md
index f4d297db..092caeee 100644
--- a/docs/frontend-api.md
+++ b/docs/frontend-api.md
@@ -198,7 +198,9 @@ GET /api/v1/workspaces/{workspace}/projects/{project}/pages
]
```
-`404` if the workspace or project doesn't exist.
+`404` if the workspace or project doesn't exist. A page whose `expires_at`
+TTL has passed is left out, as search and `recent` leave it out; the
+single-page read below still returns it.
### 4.4 Page (read full)
@@ -308,8 +310,8 @@ Rules:
GET /api/v1/workspaces/{workspace}/projects/{project}/recent?limit=20
```
-`is_latest = 1` pages ordered by `updated_at` DESC. `limit` clamped
-`1..=100`, default `10`.
+`is_latest = 1` pages whose `expires_at` TTL has not passed, ordered by
+`updated_at` DESC. `limit` clamped `1..=100`, default `10`.
Every reader surface uses the same `kind` contract. An explicit frontmatter
`kind` wins; otherwise the path families `_rules/`, `_slots/`, `sessions/`,
diff --git a/docs/usage.md b/docs/usage.md
index 34b168ff..0b364af4 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -634,7 +634,9 @@ elsewhere it searches every project with FTS5, like
a project, and its "Kind" and "Tier" selects (`kind=` and `tier=`) keep only
the pages of that kind or tier. A page shows an outline of its headings, the pages that cite it and
the pages it cites; a folder's namespace listing sorts by recent update or by
-title and shows 25 pages at a time. The search on a project page ranks with
+title and shows 25 pages at a time. The tree, the recent-activity list and a
+namespace listing leave out a page whose `expires_at` TTL has passed, as search
+does; its own URL still opens it. The search on a project page ranks with
the same hybrid ranker as `memory_query` for that project, and its "Explain
ranking" box shows each hit's stream ranks, RRF contributions, authority and rerank score, plus the per-stream timings.
Root also gets `/web/health`: hook counters (429s included), the writer queue,