Skip to content

feat(harness): continue recorded history in a new Assistant [SAP-3292] #1025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ynadge wants to merge 1 commit into from
Closed

feat(harness): continue recorded history in a new Assistant [SAP-3292] #1025

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/assistant-continue-controls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@sapiom/harness": patch
---

Continue from retained Assistant history into a new paused conversation with recorded context.
5 changes: 5 additions & 0 deletions packages/harness/docs/assistant-history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,3 +143,8 @@ If publication and rollback both fail, metadata reports an unconfirmed commit;
the new valid generation may already be readable and the previous generation is
retained. Resume reconciles its exact durable operation proof after restart.
An original-base replay cannot change the operation's committed execution state.

Continue explicitly uses the record currently displayed in history review. Its
opaque request tuple survives reloads and uncertain responses; tabs serialize
creation before POST. A verified child opens Assistant paused with recorded
provenance. Account, navigation and newer bus state fence result adoption.
Loading
Loading