yume Client Session Recovery and Rollback (Delivery)

yume Client Session Recovery and Rollback (Delivery)

1. 01

   Open the yume desktop app and navigate to the session list to identify the crashed session.

   Sessions are auto-saved every 5 minutes. Look for the most recent snapshot timestamp before the crash.

2. 02

   Select the session and click 'Restore' to reload the last 5-minute snapshot.

   This brings back the full context, including open tabs, panes, and agent states, so you can resume client work without re-prompting.

3. 03

   Review the visual diff of code changes made before the crash.

   Use the diff view to see which modifications were applied. This helps you decide whether to keep or roll back changes before continuing.

4. 04

   If any changes are unwanted, use the per-message rollback feature to revert to a previous state.

   Click on the specific message in the session history and select rollback. This is critical when an agent introduced a bug that needs to be undone.

5. 05

   Verify the restored session's token usage and remaining quota.

   Check the live token indicator to ensure you have enough budget for the remaining client tasks. If low, consider pausing non-essential agents.

6. 06

   Re-launch the necessary agents (architect, explorer, implementer, guardian) in the correct order.

   For example, run architect first to re-plan, then implementer to execute, and guardian to review. Use parallel execution on isolated branches if the task allows.

7. 07

   Document the recovery in the client's project log.

   Note the crash time, restore point, and any rollbacks performed. This transparency helps when billing for delivery hours and maintains client trust.