Skip to content

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

Rust

docs: align inbox editing migration notes with main

Aldo Junior67c3d26d5a61
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c79624a6..a13b148b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -21,7 +21,7 @@ version in [`docs/changelog/`](docs/changelog/):
with a count above the list and a way back into the editor. Editing needs
write access to the mailbox project and to the project the message came from,
and a message an agent already collected cannot be edited. Held messages use a
- new `editing` state (migration V95) that no claim path selects (#NNN).
+ new `editing` state (migration V93) that no claim path selects (#NNN).
- Added server-side response investigation to the project dashboard. Responses
can be filtered by UTC period, exact model, harness, session, turn and tool,
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
index 5d882466..cba51c08 100644
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -614,7 +614,7 @@ prunable rather than only after it ages in place.
| `token_calls` | V90 per-session native response identities with content-free input, output and cache counters. Live hooks merge partial/replayed responses with column-wise maxima in one writer transaction, then refresh cumulative session usage. Project reads authorize the project and apply session ownership before counting or ranking. V90 also converts historical Codex input totals to fresh input, excluding cache reads. |
| `agent_messages.to_agent` | V91 optional registered harness recipient; NULL keeps the shared project inbox. Both claim guards enforce addressed delivery. |
| `token_calls` context and `token_call_tools` | V92 nullable native turn/response coordinates and response time, plus bounded tool references keyed by session/response. One writer transaction persists counters, provenance and session totals; tools cascade with their response. Missing context stays unknown. Server-side UTC/model/harness/session/turn/tool filters run after scope/owner checks and before pagination. |
-| `agent_messages.state` `editing` | V95 lets a sender hold a pending message out of the queue while editing it. The claim path selects only `pending`, so a held message cannot be popped by order or by id. The row keeps its id and `created_at`, and `edited_at` records the last text change. `ops::begin_message_edit` and `finish_message_edit` are single `UPDATE`s scoped to the recipient coordinate and the expected state, so a collected, cancelled or foreign message is left alone. Saving goes through the sanitizer and `message_send` admission. |
+| `agent_messages.state` `editing` | V93 lets a sender hold a pending message out of the queue while editing it. The claim path selects only `pending`, so a held message cannot be popped by order or by id. The row keeps its id and `created_at`, and `edited_at` records the last text change. `ops::begin_message_edit` and `finish_message_edit` are single `UPDATE`s scoped to the recipient coordinate and the expected state, so a collected, cancelled or foreign message is left alone. Saving goes through the sanitizer and `message_send` admission. |
| `client_activity` | Server-wide MCP tool-call counters split into reads/writes and bucketed by UTC day. The MCP request choke point flushes buffered calls on a one-minute background interval; failed batches retry from bounded memory. Each day stores at most 128 sanitized client labels plus `other`, so an untrusted `clientInfo.name` cannot create traffic-proportional rows. |
| `auto_improve_proposals` | Staged learning and maintenance edits with immutable target snapshots and append-only decision events. Pending-target uniqueness is scoped by the qualified staging identity; unattributed proposals retain the historical shared bucket. |
| `entities`, `entity_page_links` | V38 noun index derived from canonical frontmatter. Names are normalized and unique per project; links target immutable page versions while retrieval filters to the latest version. Scope-pairing triggers prevent cross-project links. Powers the fourth RRF retrieval stream. |