Why Snag exists
Ten years as a product manager, now building. Snag is the tool I kept wishing existed — twice, for two different reasons.
As a PM, the bug report was never enough
I spent hours pulling detail out of customers and support so developers had something they could actually work with. What broke, on what page, in what order, with what in the console. The team was global, so the gaps got closed on troubleshooting calls at whatever hour both sides could manage.
As a builder, I was the copy-paste layer
When I started shipping code myself the pain moved but did not go away. I was copying logs out of one window and pasting them into a CLI so an agent had enough context to fix the bug. I was doing by hand exactly what I used to ask developers to wait for.
So Snag does both halves
A reporter clicks once and the evidence comes with the bug — replay, console, network, repro steps. Then your coding agent reads that evidence directly, over MCP, and opens a pull request for a human to review. Nobody transcribes anything.
Who is behind it
Snag is built by Drew Stockler, and operated by Digital Ventures Conglomerate Limited. Snag is early — the first 50 workspaces are grandfathered on purpose. If you want to talk to the person building it, that is admin@dvcllc.io, and it reaches me.