Configuration
Vreko works out of the box. Snapshots are created automatically based on risk detection and AI activity. Configure only when you need customization.
Quick Reference
Protection Levels
Watch, Warn, Block - control how files are protected
AI Detection
Automatic AI tool detection - no configuration needed
Storage
Customize where snapshots are stored
MCP Integration
Connect AI assistants to Vreko
Protection Levels
| Level | Behavior | Best For |
|---|---|---|
| 🟢 Watch | Silent auto-snapshots | Source code, docs |
| 🟡 Warn | Proceed with risk boost | Config files, dependencies |
| 🔴 Block | Hard stop, no write | Secrets, .env*, credentials |
Automatic by default. Vreko assigns protection levels based on file type. Most files get watch, config files get warn, and sensitive files get block. You rarely need to change this.
Pattern-Based Rules
Create .vrekorc in your project root to customize:
{
"protection": [
{ "pattern": "src/auth/**/*", "level": "block" },
{ "pattern": "package.json", "level": "warn" },
{ "pattern": "**/*.md", "level": "watch" }
],
"ignore": ["*.test.ts", "**/*.spec.ts"]
}AI Detection
Works automatically. Vreko detects Cursor, GitHub Copilot, Claude Code, and Windsurf with 89% accuracy. No configuration required.
Settings
| Setting | Default | Description |
|---|---|---|
snapshot.sensitivity | "medium" | Detection sensitivity: "low" / "medium" / "high" |
aiDetection.confidenceThreshold | 6 | Minimum confidence to trigger (0-10 scale) |
snapshot.aiDetectionEnabled | true | Enable AI-triggered snapshots |
Higher sensitivity = more snapshots during AI activity.
Lower sensitivity = fewer snapshots, only on confident detection.
Storage
| Setting | Default | Description |
|---|---|---|
settings.snapshotLocation | .vreko/ | Where snapshots are stored |
settings.maxStorageSize | 500 | Maximum storage in MB |
settings.maxSnapshots | 100 | Maximum snapshots to retain |
Custom Storage Location
{
"settings": {
"snapshotLocation": "~/vreko-storage",
"maxStorageSize": 1000,
"maxSnapshots": 200
}
}MCP Integration
VS Code handles this automatically. The Vreko extension configures MCP for Cursor, Windsurf, and VS Code-based editors. This section is for standalone setup (Claude Desktop, etc.).
Settings
| Setting | Default | Description |
|---|---|---|
mcp.enabled | true | Enable MCP integration |
mcp.serverUrl | https://mcp.vreko.dev | MCP server endpoint |
mcp.timeout | 5000 | Request timeout in milliseconds |
Configure AI Assistants
# Claude Desktop
vreko tools configure --claude
# Windsurf
vreko tools configure --windsurf
# All detected assistants
vreko tools configure --allVS Code Settings
Access via ⌘+, → Search “vreko”:
| Setting | Default | Description |
|---|---|---|
vreko.protectionLevels.defaultLevel | "watch" | Default protection for new files |
vreko.snapshot.aiDetectionEnabled | true | AI-triggered snapshots |
vreko.mcp.enabled | true | MCP integration |
vreko.mcp.serverUrl | https://mcp.vreko.dev | MCP server URL |
.vrekoignore
Exclude files from protection (similar to .gitignore):
# Dependencies
node_modules/
.pnpm-store/
# Build outputs
dist/
.next/
build/
# Logs
*.log
logs/
# Large files
*.mp4
*.zipEnvironment Variables
| Variable | Description |
|---|---|
VREKO_STORAGE_PATH | Override snapshot storage location |
VREKO_DEBUG | Enable debug logging (true/false) |
VREKO_DISABLE_TELEMETRY | Disable anonymous telemetry |