Automatic Protection
🧢 SnapBack now uses the AutoDecisionEngine for automatic, intelligent protection.
No manual configuration required—SnapBack figures out what to protect and when.
Zero-Config Protection
SnapBack’s AutoDecisionEngine automatically detects when to create snapshots based on:
- AI Activity Detection — Recognizes changes from Cursor, Copilot, Claude Code, and Windsurf
- Risk Scoring — Evaluates file criticality and change scope
- Burst Detection — Identifies rapid multi-file changes typical of AI refactoring
- Pattern Learning — Gets smarter over time by learning from your workflow
Protected
AutoDecisionEngine is actively monitoring your code and creating snapshots when needed.
Monitoring
SnapBack is watching for AI activity and risky changes, ready to snapshot instantly.
How AutoDecisionEngine Works
The AutoDecisionEngine evaluates every file save and makes intelligent decisions:
- Should we snapshot? Based on aggregated risk signals
- How urgent is it? Confidence scoring from AI detection accuracy
- What triggered it? Attribution for learning and improvement
Automatic Snapshot Triggers
- AI tool detected making substantial changes
- Critical files modified (auth, config, database)
- Multiple files changed rapidly (AI refactoring pattern)
- High-risk change patterns detected
- Significant time since last save point
What Gets Protected
✅ Protected by Default
- • All source code (
.js,.ts,.py, etc.) - • Configuration files (
.json,.yaml,.toml) - • Environment files (
.env*) - • Documentation (
.md,.mdx) - • Build configs (
package.json,tsconfig.json)
❌ Not Protected
- •
.git/directory - •
node_modules/and dependency folders - • Build outputs (
dist/,.next/) - • Binary files and logs
Customizing Protection (Optional)
While AutoDecisionEngine handles most cases automatically, you can customize with .snapbackrc:
// .snapbackrc
{
"include": ["src/**/*", "config/**/*"],
"exclude": ["*.test.ts", "*.spec.ts"],
"alwaysProtect": ["src/auth/**/*", ".env*"],
"neverProtect": ["*.generated.ts"]
}💡 Recommended: Let AutoDecisionEngine learn your patterns for 30 days before adding custom rules. It’s usually smarter than manual configuration.
The Learning Loop
SnapBack gets smarter the longer you use it:
🌱 Day 1: Common Patterns
Catches hardcoded secrets, phantom dependencies, test code in production, risky refactoring patterns.
🌳 Day 30: Your Patterns
Learns YOUR codebase: which auth modules Cursor breaks, which refactor patterns cause issues, which folders have phantom dependency problems.
🌲 Month 3: Proactive Protection
Catches issues before you notice: folder-specific risks, pattern-specific risks, tool-specific risks.
Status Indicators
| Icon | State | Meaning |
|---|---|---|
| 🟢 | Protected | AutoDecisionEngine active |
| 🟡 | Monitoring | Watching for AI activity |
| 🔴 | Paused | Protection temporarily disabled |
Related Documentation
- How Protection Works - Deep dive into AutoDecisionEngine
- AI Detection - How SnapBack monitors AI coding assistants
- Session Time-Travel - Multi-file atomic rollback for AI changes
- CLI Documentation - Command-line interface for automation
✅ Zero Configuration Required: SnapBack protects your code automatically from day one. Just install and start coding—we’ve got your back.