Skip to content

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

Rust

docs: polish PR 24 prose with humanizer

Aldo Junior0a997170f25a
diff --git a/docs/agent-messaging.md b/docs/agent-messaging.md
index 0c5ca0eb..8e95bd3d 100644
--- a/docs/agent-messaging.md
+++ b/docs/agent-messaging.md
@@ -341,11 +341,10 @@ its original place in the queue. "Discard changes" puts it back unchanged. The
message keeps its id either way. A message an agent collected in the meantime
cannot be edited, and the editor says so. Editing needs write access to the
project that holds the mailbox and to the project the message came from, the
-same access that sending it needed. While held, a message shows as Editing, a
-banner above the list counts the held messages and links to them, and Continue
-editing or Discard changes works from any tab. A held message stays out of the
-queue until someone saves or discards it, so an editor left open in a closed tab
-keeps it from the agent until it is released. The legacy GET-only login cannot
+same access that sending it needed. Held messages show as Editing. A banner above the list counts them and links
+to them; Continue editing and Discard changes work from any tab. Closing an
+editor tab leaves the message held outside the queue until someone saves or
+discards it. The legacy GET-only login cannot
edit.
Queuing a message does not start or wake an agent, or authorize it to follow
diff --git a/docs/frontend-api.md b/docs/frontend-api.md
index da9dd746..c1583eb0 100644
--- a/docs/frontend-api.md
+++ b/docs/frontend-api.md
@@ -1022,13 +1022,13 @@ the UI header and the normal browser-session CSRF checks. It does not mutate
wiki pages, pop messages or run an agent. See
[agent messaging](agent-messaging.md#in-the-web-ui).
-Three more POST routes edit a queued message: `/web/messages/{id}/edit` holds it
+Three additional POST routes support editing queued messages: `/web/messages/{id}/edit` holds it
out of the queue and returns its text, `/web/messages/{id}/save` replaces the
subject and text and requeues it, and `/web/messages/{id}/release` requeues it
unchanged. The body names the mailbox (`workspace`, `project`), and `save` adds
`subject` and `body`. They need the same checks as sending, plus write access to
-the project the message came from. A message that is not in the expected state
-answers 409.
+the project the message came from. A message outside the expected state
+returns 409.
## Bundled documentation for agents
diff --git a/docs/usage.md b/docs/usage.md
index e2d16f86..2fba88af 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -987,9 +987,9 @@ Expanding a row shows its plain text. New message picks a source project and a
recipient harness from the agents that already have sessions in visible
projects. Sending needs write access to both projects and goes through the
configured sanitizer and message admission policy. Browser sessions use the
-existing CSRF checks. A queued message has an Edit button. It takes the message
-out of the queue while you change its subject or text, and it goes back, in its
-original place, when you save or discard. A message an agent already collected
+existing CSRF checks. A queued message has an Edit button. The message leaves the
+queue while you change its subject or text. Saving or discarding returns it to
+its original place. A message an agent already collected
cannot be edited.
A queued request does not launch an agent. The addressed harness collects it the