context-restore

To restore a saved working context after switching branches, use the /context-restore command. It reads the most recent saved state and integrates it deterministically into your current session so you can resume interrupted tasks immediately.

Context restoration works by automatically loading the most recent saved state when you switch Conductor workspaces. It reads the previously saved checkpoint and applies it to the new session, allowing you to continue exactly where you left off.

Yes, you can resume interrupted tasks across multiple branches by restoring your saved context. The process reads your most recent checkpoint and integrates it into the current session deterministically, preserving your working state across branch switches.

Yes, you need to pair /context-restore with a /context-save command beforehand. Saving your context creates the checkpoint state that the restore command later reads and integrates into your new session when you switch branches or workspaces.

The best way to maintain consistent context across sessions is to pair a context save command with /context-restore. This workflow captures your working state as a checkpoint and deterministically loads the most recent one when you resume.

Restored context loads the most recent saved state deterministically. If the context does not match, ensure you executed a context save before switching branches, as the restore command relies on that checkpoint to integrate state into the current session.