branching-workflow

To recover an off-the-rails agent session, you orchestrate a transition from corrupted execution paths to clean prior states. This structured workflow extracts valuable learnings, notes side effects, and forks the session to a productive path.

You should branch an agent session instead of revising in place when structural errors or context drift necessitate a controlled reset. A decision framework helps determine when to fork the session versus attempting direct corrections.

To safely rewind conversation history without losing durable learnings, adhere to the /save-before-rewind protocol. This ensures critical insights and side-effect tracking are persisted before discarding corrupted execution paths.

The best way to fix context pollution during complex coding tasks is to apply a recovery primitive that standardizes the /rewind command. This safely discards corrupted conversation history and restarts from a clean prior state.

Yes, you can reset agent context drift without losing side-effect tracking by following the /save-before-rewind protocol. Noting side effects before destruction ensures critical insights persist when you fork the session.

Executing a branching workflow requires saving before destruction to ensure the persistence of durable learnings and side-effect tracking. This safety guardrail prevents losing critical insights when discarding corrupted conversation history.