dsh-web-recorder

Getting an agent to drive a business platform through its APIs starts with a hard question: which endpoints exist, which business step triggers which call, and what do the request and response shapes actually look like. The usual path — reading API docs or reverse-engineering frontend code — falls apart when documentation is missing or stale, and even a complete endpoint list rarely maps on-screen actions to the backend calls they fire. dsh-web-recorder takes a different approach: no reverse engineering, just capture the operating evidence.

The plugin launches a monitored headed browser window (or attaches to one already open via CDP). As you click, type, and submit forms — by hand or through Playwright MCP or any browser-use driver — it records every UI event and every xhr/fetch request and response side by side on a single timeline in events.jsonl. Any business step can be traced to the exact interface it called, the parameters it sent, and the response it received. Stopping the recorder produces a report.md that lays out the operation timeline and request details in a readable summary, ready for an LLM to distill into interface-level skills.

It is built for developers and agent engineers who need to quickly reverse-map an unfamiliar web platform into a reusable automation contract without hunting through documentation. The browser driver can be a real person clicking in the popup window, Playwright MCP, or any browser-use tool — none of them are hard dependencies. The core artifacts stay the same: a raw event stream and a structured report that give the model everything it needs to analyze, summarize, and codify the workflow.