mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-10 18:35:17 +00:00
Mohamed Boudra
dc85c2bfbc
Reload agent used to delete the timeline and replay the provider's history under a new epoch. That brought back turns the user had rewound and dropped anything the provider no longer had. Archive deleted the timeline too. Paseo's timeline is now the owner of the conversation. Reload agent keeps it and reconciles the provider's history append-only: turns are aligned by provider prompt id and compared exactly (prompt text, assistant and reasoning text, tool calls). When the owned conversation is a whole-segment prefix of the provider's, the rows after it are appended as new live rows. Any other difference changes nothing and agent_refreshed reports historyDiverged, which the app shows as a warning on Reload agent and Unarchive. Divergence is deliberately conservative: - An answer or tool call Paseo saw only partly can never be completed by a reload. History rows carry no turn id to update a live row in place. - A prompt sent with attachments diverges on every reload. Providers store the rendered attachment text, and the owned row keeps only the typed text. Recording the sent prompt is left to provider handoff work. Archive now only closes the runtime. Stored history, including provider children, is read without resuming or even requiring the provider. Forced provider replacement is removed. Tradeoff: an archived chat's history stays in memory until the daemon exits, measured at about 1.1-1.2x its JSON size (about 0.5 MB for a typical session, about 16 MB for a heavy tool session). Moving retained history to disk belongs to the persisted backend, not eviction, which would drop the rewinds this change keeps.
@getpaseo/protocol
Shared Paseo protocol schemas, codecs, and wire types.
Stability
This package is public so Paseo's published packages can depend on it cleanly. It is not a stable public API yet.
Schemas, exports, wire helpers, and types may change or disappear in any release without advance notice. Use it outside Paseo at your own risk until the package is explicitly documented as stable.