"Travel" matching MCP servers:

Records every browser session (screen, DOM, network, console, storage) and enables time-travel debugging to rewind and analyze failures.

Enables time-travel debugging for AI agent sandboxes using Firecracker microVMs, with tools for code execution, file operations, and VM snapshot/restore via MCP.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r