Add durable hosted conversation history - #35
Draft
roackb2 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
hostedConversation.recenttRPC query and a recent-conversation UI with conditional polling for open turns, local retry/error states, truthful failure/interruption presentation, and the existing hardened Markdown policy.Why
Hosted answers and progress previously lived only in React state, so a refresh erased the only user-visible record of a completed or interrupted agent turn. This change gives the product a durable, inspectable terminal history without persisting raw execution traces or introducing replay semantics.
Privacy and lifecycle boundaries
The projection stores only user/workspace/invocation identifiers, the prompt, bounded public terminal Markdown, a closed set of Lucid-owned lifecycle codes, and timestamps. It deliberately excludes activity, hidden reasoning, tool inputs/results, credentials, capabilities, traces, provider error messages, and provider error codes.
Only an explicit terminal cancellation is recorded as cancelled. Browser disconnects and service shutdown use the truthful interrupted state because the shared HTTP abort signal cannot prove user intent. Expired open rows converge through user-scoped reconciliation and conditional client polling.
Validation
LUCID_POSTGRES_TEST_URL='postgresql:///lucid_test' yarn test— 148 server, 24 web, and 4 simulator tests passedyarn typecheckyarn buildyarn server:db:generate— no schema driftgit diff --check