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
Copy file name to clipboardExpand all lines: docs/en/api/05-sessions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1403,8 +1403,8 @@ Commit a session. Message archiving (Phase 1) completes immediately. Summary gen
1403
1403
**Notes:**
1404
1404
- Rapid consecutive commits on the same session are accepted; each request gets its own `task_id`.
1405
1405
- Empty sessions, or commits where all messages remain inside `keep_recent_count`, complete synchronously with `archived: false`.
1406
-
- Background Phase 2 work is serialized by archive order: archive `N+1` waits until archive `N` writes `.done`.
1407
-
- If an earlier archive failed and left no `.done`, later commit requests fail with `FAILED_PRECONDITION` until that failure is resolved.
1406
+
- Background Phase 2 work is serialized by archive order while the direct predecessor is still pending.
1407
+
- If Phase 1 archived messages but Phase 2 later fails, the archive is marked with `.failed.json`. That failed archive is terminal and skippable: it is not returned as a completed archive, it does not provide an overview, and it does not block later commit requests.
1408
1408
- If committed messages contain durable facts, judgments, preferences, or events that mention `viking://resources/...`, memory extraction preserves the resource as a markdown link and records it in `MEMORY_FIELDS.resource_refs`.
Copy file name to clipboardExpand all lines: examples/openclaw-plugin/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -229,6 +229,7 @@ Use it as a complement to auto-capture, not a replacement:
229
229
- it calls `commit(wait=true)` and blocks for completion
230
230
- when an archive exists, it re-reads `latest_archive_overview`
231
231
- it returns updated token estimates, the latest archive id, and summary content
232
+
- if archiving succeeds but Phase 2 reaches a failed terminal state, the compact boundary is still reported as established, with a degraded reason and the task details attached
232
233
- if the summary is too coarse, the model can call `ov_archive_expand` to reopen a specific archive
233
234
234
235
So `afterTurn()` is closer to "incremental append plus threshold-triggered async commit", while `compact()` is the explicit "wait for archive and compaction to finish" boundary.
0 commit comments