Give your AI the superpower of traveling back in time to find what went wrong and fix the timeline. 🌐 Website • 🎉 Start Free • 📖 Docs --- 🚀 Quick Start (30 seconds) Option 1: One-Line Setup Follow the prompts to sign in with Google and auto-configure your MCP client. Option 2: With License Key Option 3: Manual Config Add to your MCP client config (Claude Code, Cursor, etc.): **That's it!** 🎊 Ask your AI: *"Debug my crashing program"* --- ⏱️ What It Does **Time-travel debugging for AI workflows.** Step forward. Step backward. Debug as if the bug never existed. | Feature | Description | |---------|-------------| | ⏪ **Step Backward** | Rewind execution to find root causes | | ⏩ **Step Forward** | Resume from any checkpoint | | 🎯 **Breakpoints** | Hardware-level with hit counting | | 📚 **Stack Traces** | SIMD-accelerated unwinding | | 🔐 **Audit Trail** | Hash-chain integrity for compliance | --- 💜 How It Works **No local installation.** Works on macOS, Windows, Linux via MCP. --- 🏷️ Pricing | Tier | Price | Sessions | |------|-------|----------| | 🆓 **Hobby** | Free | 5/month (unlimited during 7-day trial!) | | 💎 **Pro** | $19/mo | 100/month + unlimited time-travel | | 🔧 **Engineer** | $49/mo | 500/month + memory replay + LSH bug search | | 👥 **Teams** | $129/mo | 2,000/month + team audit logs | | 🏢 **Enterprise** | Custom | Unlimited + SOX/SOC2/GDPR/HIPAA compliance | **Start Free →** --- 🛠️ MCP Tools Your AI gets these debugging superpowers: - debugger_attach - Connect to a process - debugger_set_breakpoint - Set breakpoints - debugger_continue - Resume execution - debugger_step_forward - Step forward - debugger_step_backward - ⏪ Step backward in time - debugger_get_stack_trace - Get stack trace - debugger_get_variables - Read memory - debugger_export_trace - Export execution trace --- 💬 Example **You:** "My Rust program crashes at runtime. PID is 12345" **AI:** --- 📞 Support