rm -rf / Generate shell commands that work the first time—with pre-execution validation that catches what AI gets wrong. 100% local. Privacy-first. Your commands never leave your machine.
Natural language in. Safe, working commands out.
Caro warns you before you wipe critical logs
Platform-aware commands that work the first time
rm -rf / rm -rf ~ :(){ :|:& };: dd if=/dev/zero of=/dev/sda chmod -R 777 / mkfs.ext4 /dev/sda1 52+ dangerous patterns detected and blocked automatically
See the specific risks Caro catches for your workflow
rm -rf /var/log/* docker system prune -a --volumes -f chmod -R 777 /var/www systemctl restart * find / -size +100M -delete kubectl delete pods --all -n production rm -rf ~/backups/db* pkill -9 -f java git push --force origin main rm -rf /data/tmp/* DROP TABLE users_backup; kafka-consumer-groups --reset-offsets --to-earliest --all-topics --execute Real concerns from the community that shaped Caro
"If AI can code 100x faster, why aren't you shipping 100x faster? Because AI code is not production-ready code..."
"Running rm is risky. Running it with * is 10x more dangerous. Running rm -rf /* is catastrophic."
"In the age of AI, save your engineers for the platform. The rise of AI-powered development tools is ushering in a new paradigm..."
Caro doesn't just block dangerous commands—it explains why they're dangerous and suggests safer alternatives. You stay in control while learning from every interaction.
Specific experiences, not generic praise
"Caught a recursive delete pattern I would have missed at 2 AM during an incident. The warning was specific enough that I understood WHY it was dangerous."
"We use it for onboarding. New engineers learn shell safety while being productive. No more scary 'don't touch production' lectures—Caro teaches in context."
"Compliance asked if our AI tools send data externally. Showed them Caro's source code—100% local. Approved same day. That never happens."
Don't take our word for it—
Read the source code, verify the claimsBuilt for engineers who can't afford to get it wrong
Blocks rm -rf /, fork bombs, and 50+ other career-ending commands BEFORE you can run them. Your 2 AM self will thank you.
Privacy-first design. No cloud API calls. Run in air-gapped networks. Pass any compliance audit. Your commands never leave your machine.
Generates commands that work on your Mac, your Linux server, and your coworker's BSD box. First time. Every time.
Sub-2s inference on Apple Silicon. No waiting for cloud APIs. No wondering if the server is down. Just answers.
See exactly what Caro blocks and why
View safety patterns →The differences that matter
Your production commands, server names, and file paths never leave your machine. Ever.
52+ safety patterns including rm -rf, fork bombs, and disk wipes. Pre-execution, not post-mortem.
Detects your OS, knows BSD vs GNU, and adjusts syntax automatically. No more Stack Overflow.
Real questions from skeptical engineers (we get it)
Caro's safety patterns are baked into the binary—no network needed. When you update Caro (cargo install caro --force), you get the latest patterns. The core dangerous commands (rm -rf /, fork bombs, disk wipers) don't change. We also accept pattern contributions via GitHub.
No. Caro adds <100ms to command generation. The safety check is instant (pattern matching, not AI inference). In a real incident, that's 100ms that might save you from making things 10x worse. The validation is synchronous—you see the warning immediately.
Caro detects your OS and shell at runtime. On macOS, it knows you're using BSD tools. On Linux, it adjusts for GNU syntax. It reads your $SHELL and adjusts accordingly. No configuration needed—it just works.
Caro warns, it doesn't jail. When you see a warning, you can still proceed—we just make sure you're doing it intentionally. For truly destructive commands (rm -rf /), you'll need to confirm. This is your seatbelt, not a straitjacket.
No. Caro runs 100% locally. Your commands, file paths, server names, and directory structures never leave your machine. The inference happens on your hardware. We collect minimal, anonymous usage metrics to improve the product—see our telemetry page for details. Check the source code—it's AGPL-3.0 licensed.
You shouldn't trust them blindly—that's the point. Caro generates commands AND validates them before you run them. It's not 'trust the AI'—it's 'trust the pattern-based safety layer that catches what the AI might get wrong.' The validation is deterministic, not probabilistic.
Still skeptical? Good—you should be.
Read the source code →No account. No API key. No data collection. Just safer shell commands.
bash <(curl --proto '=https' --tlsv1.2 -sSfL https://setup.caro.sh) Then run:
caro "find files modified in the last 7 days" Prefer to build from source? See all installation options →