Workspace Snapshots

Checkpoints serve as an automated safety net, frequently versioning your local files as you interact with Sypha. This allows you to explore AI proposals with total confidence, knowing you can revert the environment to any prior state instantly.

Advantages of Versioned Snapshots

• Fearless Iteration: Validate complex AI refactors without risking your stable code.
• Instant Rollback: Recover your project immediately if a suggested path proves incompatible.
• Version Comparison: Rapidly toggle between different implementation strategies to find the ideal solution.

Underlying Mechanism

Sypha manages a dedicated shadow repository specifically for snapshots, which operates independently from your primary version control. No external hosting or initial Git configuration is needed for this to work.

[!NOTE] Ensure a Git client is installed on your local machine, as it powers the underlying versioning engine.

Interacting with Snapshots

You will find snapshots logged directly within your conversation thread:

• Task Origin: Captures your project's state the moment a task begins.
• Incremental Points: Automatically generated after significant edits or shell commands.

Restorative Options

1. Inspect Changes: View a granular diff between your current files and the snapshot (highlighting additions and subtractions).
2. Apply Snapshot:
   • Environment Only: Reverts the source code while preserving the conversation context - ideal for refining the original plan.
   • Full State: Synchronizes both the file system and the AI's memory to that exact moment in time.

Settings

Configure snapshot behavior via Settings -> Checkpoints.

• Automatic Versioning: Toggle whether Sypha creates snapshots automatically (enabled by default).

Technical Overview

• Storage Optimization: To maintain high performance, build outputs (node_modules), large binaries, and assets are excluded from snapshots.
• Ignore Protocols: Sypha honors existing .gitignore and .syphaignore files.
• Complex Hierarchies: Supports projects with nested repositories and multi-root workspaces.