• ⚡ One-Key Snapshots: Ctrl+Alt+S - instant backup
• 🔄 Time Navigation: Jump between any point in your development
• 📊 Visual Timeline: See your progress in the Snapshots panel
• 📈 Status Tracking: Status bar shows time since last snapshot
• 🔍 Smart Search: Find code across all snapshots (Experimental)

• 📝 Rich Context: Add tags, notes, and task references
• ⭐ Favorites: Mark important snapshots
• 🔍 Powerful Filtering: By date, tags, files, or favorites
• 📋 Selective Snapshots: Choose specific files to include
• 🔄 File Restoration: Restore individual files or entire snapshots

• ⏰ Auto-Snapshots: Time-based automatic backups
• 📋 Smart Rules: Auto-snapshot specific file patterns
• 📊 Visual Indicators: See changed lines in editor gutters
• ⚡ Performance: Efficient storage with differential compression
• 🚫 Smart Exclusion: Respects .gitignore and .snapshotignore

• 📝 Branch Context: Store Git branch/commit info with snapshots
• 🔄 Git Commands: Create commits directly from snapshots
• 🛡️ Safety Net: Auto-snapshot before Git operations
• 🤝 Perfect Harmony: Works alongside Git without conflicts

Interactive Development Workflow

# Create checkpoint before risky changes
codelapse snapshot create "Before refactoring auth system" --tags "checkpoint,auth"

# Work on your code...

# Create snapshot after major milestone
codelapse snapshot create "Auth refactor complete" --tags "feature,auth" --favorite

# Compare changes between snapshots
codelapse snapshot compare snapshot-123 snapshot-124

# Navigate through your development timeline
codelapse snapshot navigate next

Code Review & Collaboration

# Export snapshot for sharing with team
codelapse utility export snapshot-123 --format zip --output ./auth-feature.zip

# Validate snapshot integrity before sharing
codelapse utility validate snapshot-123

# Show detailed snapshot with specific file content
codelapse snapshot show snapshot-123 --files --content src/auth.ts

Safety-First AI Operations

# 1. ALWAYS create backup before AI operations
BACKUP_ID=$(codelapse snapshot create "AI: Pre-operation backup" --tags "backup,ai" --json --silent | jq -r '.snapshot.id')

# 2. Execute AI operations with error handling
if codelapse snapshot restore snapshot-123 --backup --json --silent; then
  echo "✅ Operation successful"
else
  echo "❌ Operation failed, restoring backup"
  codelapse snapshot restore "$BACKUP_ID" --json --silent
fi

# 3. Document completed work
codelapse snapshot create "AI: Completed refactoring task" --tags "complete,ai" --favorite --json --silent

Batch Processing & Real-time Monitoring

# Execute multiple operations from JSON file
cat > ai-workflow.json << EOF
[
  { "method": "takeSnapshot", "data": { "description": "Pre-operation backup", "tags": ["backup"] } },
  { "method": "getSnapshots", "data": { "tags": ["feature"], "limit": 5 } },
  { "method": "takeSnapshot", "data": { "description": "Post-operation state", "tags": ["complete"] } }
]
EOF

codelapse batch ai-workflow.json --json --silent

# Monitor workspace changes for reactive workflows
codelapse watch --events snapshots,workspace --json | while read -r event; do
  echo "Processing event: $event"
  # Add your AI logic here
done

CI/CD Pipeline Integration

# Pre-deployment snapshot with Git context
codelapse snapshot create "Pre-deployment: $(git rev-parse --short HEAD)" \
  --tags "deployment,$(git branch --show-current)" --json --silent

# Validate workspace state before deployment
codelapse workspace state --json --silent

# Create release snapshot with version tagging
codelapse snapshot create "Release v$(cat package.json | jq -r .version)" \
  --tags "release,production" --favorite --json --silent

Automated Testing Workflows

# Create test checkpoint
codelapse snapshot create "Before test run" --tags "test,checkpoint" --json --silent

# Run tests and capture results
if npm test; then
  codelapse snapshot create "Tests passed: $(date)" --tags "test,success" --json --silent
else
  codelapse snapshot create "Tests failed: $(date)" --tags "test,failure" --json --silent
  # Optionally restore to last known good state
  codelapse snapshot restore last-good-snapshot --backup --json --silent
fi

name: CodeLapse Integration
on: [push, pull_request]

jobs:
  test-with-codelapse:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '18'
      
      - name: Install CodeLapse CLI
        run: npm install -g codelapse-cli
      
      - name: Create pre-test snapshot
        run: codelapse snapshot create "CI: Pre-test snapshot" --tags "ci,test" --json --silent
      
      - name: Run tests
        run: npm test
      
      - name: Create post-test snapshot
        run: codelapse snapshot create "CI: Post-test snapshot" --tags "ci,success" --json --silent

FROM node:18-alpine

# Install CodeLapse CLI
RUN npm install -g codelapse-cli

# Copy application
COPY . /app
WORKDIR /app

# Create deployment snapshot
RUN codelapse snapshot create "Docker: Pre-build snapshot" --tags "docker,build" --json --silent || true

# Build application
RUN npm install && npm run build

# Create post-build snapshot
RUN codelapse snapshot create "Docker: Post-build snapshot" --tags "docker,complete" --json --silent || true

• vscode-snapshots.snapshotLocation: Where to store snapshot data (default: .snapshots)
• vscode-snapshots.maxSnapshots: Maximum number of snapshots to keep (default: 50)
• vscode-snapshots.autoSnapshotInterval: Interval for automatic snapshots in minutes (default: 0 - disabled)
• vscode-snapshots.loggingEnabled: Enable detailed logging (default: true)

• vscode-snapshots.git.addCommitInfo: Store Git branch/commit with snapshots (default: true)
• vscode-snapshots.git.commitFromSnapshotEnabled: Enable "Create Git Commit from Snapshot" command (default: true)
• vscode-snapshots.git.autoSnapshotBeforeOperation: Auto-snapshot before Git pull/merge/rebase (default: false)

⚠️ EXPERIMENTAL FEATURE - SECURITY RISKS:

• Data Privacy: Your code is sent to external AI services (Pinecone, Gemini)
• API Key Security: Third-party services require API keys with potential access risks
• Network Exposure: Code content transmitted over internet to external providers
• Quota Costs: API usage may incur charges on your accounts
• Functionality Changes: Features may change or be removed without notice
• NOT RECOMMENDED for proprietary, sensitive, or confidential codebases

Basic Settings:

• vscode-snapshots.semanticSearch.enabled: Enable semantic code search (default: true)
• vscode-snapshots.semanticSearch.chunkSize: Maximum token size for code chunks (default: 200)
• vscode-snapshots.semanticSearch.chunkOverlap: Overlap between chunks in tokens (default: 50)
• vscode-snapshots.semanticSearch.autoIndex: Auto-index snapshots in background (default: false)

🔑 API Key Management & Security:

• Secure Storage: API keys are stored using VS Code's SecretStorage (encrypted)
• Access Control: Keys are never logged or displayed in plain text
• Configuration: Manage keys via Settings view in Snapshot Explorer
• Required Services:
  • Pinecone API Key: For vector database storage and retrieval
  • Gemini API Key: For semantic code analysis and embeddings

🛡️ Security Best Practices:

• Use dedicated API keys with minimal permissions
• Monitor API usage and costs regularly
• Disable feature when working with sensitive code
• Review API provider terms of service
• Consider network security implications

🚫 How to Disable:

1. Set vscode-snapshots.semanticSearch.enabled to false, OR
2. Use Settings view in Snapshot Explorer → Semantic Search → Disable