raindrop-add-readonly-replay

Replay production traces safely by enabling a per-run Readonly mode that prevents destructive side effects while debugging against your local agent code. This isolation ensures your replay sessions carry zero risk to production data or user impact.

Per-run readonly mode is a guard that isolates side effects when replaying production traces against a real agent. It instruments side-effect points to prevent destructive operations during local debugging sessions.

Create a replay server by scaffolding an HTTP /replay endpoint and registering your agent in the ~/.raindrop/agents.json registry. This allows Workshop to route replay requests to your local agent code.

Yes, you can debug end-to-end agent traces using Workshop's Local Agent flow by wiring a per-call readonly guard and updating your package.json. Workshop reaches your local agent through the registered agents.json routing.

Replaying production traces in readonly mode requires instrumenting all side-effect points to ensure destructive operations are caught. If side effects are not properly wired with a per-call guard, the readonly isolation may fail to prevent unintended impacts.