mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-10 18:35:17 +00:00
Mohamed Boudra
5ed1f8d108
Rewinding a prompt used to rotate the timeline epoch, so every open client refetched and remounted the whole chat. A rewind is now a retirement: the daemon keeps the rewound turn stored but outside the conversation, and capable clients remove the rows that started in [retireFromSeq, seq) in place. Catch-up pages carry the retirements in their span. Clients without the timeline_rewind_operations capability get the old replacement shape. The daemon retires only what the provider actually removed. Providers report the boundary they kept. A failure known to change nothing keeps the conversation. Any other failure leaves the rewind open and refuses prompts until reloading the agent proves the outcome from the provider's replayed prompts. A recorded cut whose save failed is committed by the next prompt or the reload, which resumes the rewound session. Plugin providers complete session.revert without saying what they removed. Paseo then reloads the session itself and judges the outcome from the replay, so a no-op completion is not taken as a cut. The app anchors each row at the seq it started at, because a late update moves a row's latest seq into the rewound range. The app also refuses pages served before the newest retirement it has seen, then refetches them. Known limits: - The automatic plugin settle shows the agent as restoring briefly. - An empty or mismatched plugin replay leaves the rewind unresolved. Fork the chat to recover. - A plugin's failed revert still needs a manual reload. - An open rewind lives in memory, so a daemon restart drops it.