Keep the canvas for sign-off. Send the bugs here.

Snag is not a review canvas and does not try to be one. It is where the defects go once the sign-off is done: one snippet on the site, a replay with the console and the network in every report, and a fix run that answers in a pull request. One flat price covers everybody who touches it, and your first 5 fixes are on us.

Why teams move to Snag

Teams rarely move because something stopped working. They move because two different jobs had been arriving in the same place, and sign-off and bug triage want different tools. The bill is where you notice first. The Pastel Pro plan costs $29 a month when billed annually, stated on their plans page as $350 for the year, and $35 a month when billed monthly, and each additional user costs $24. A Snag workspace is one figure that counts nobody, so putting the two engineers who will actually do the fixing on it costs nothing at all. You notice a second time in the report itself. A comment in Pastel arrives with the browser, the screen size and a screenshot of where it was left, which describes what the page looked like. A Snag capture describes what the page was doing: the DOM played back, the console errors in the order they happened, the requests that failed. The first of those is what you hand a designer. The second is what a coding agent has to have before it can reproduce anything.

What carries over

The reflex survives the move. Somebody sees a problem, says so on the spot, and nobody asks them to make an account first — that works the same way here, off a snippet on the site rather than off a link you sent round. What changes is the parcel that arrives. It carries the session replay, the console and the network, with personal data masked in the browser before anything uploads — inputs are never recorded. It lands as a ticket in Jira or GitHub that links back to the recording. If a coding agent already picks work up out of your feedback tool, it can carry on doing exactly that: the MCP server hands it that parcel from the Capture plan up. The built-in fix run is there for the weeks when nobody wants to babysit an agent.

What you give up

Three rows go to Pastel, and none of them are close. Timestamped video review is the first: Snag records a browser session and has nothing at all to say about a comment left against a moment in a video. The Pastel plans page names six project destinations, where Snag connects Jira and GitHub. Nineteen tools sit behind the Pastel MCP server, where the Snag server deliberately only hands out evidence. If signing off designs and videos is the actual job, Pastel is the better pick.

How switching works

Snag imports nothing, so this is a clean start rather than a migration. Three things to do: drop the snippet into the site, tell Snag which domain it may record on, and connect Jira or GitHub. Nobody buys a licence to file a report, so no roster gets rebuilt and no per-person line reappears on the invoice. After that, every capture is a candidate for a fix run and every fix run ends at a pull request somebody reads; Snag never auto-merges, and the agent never works outside a sandbox that is destroyed when the run ends.

Weighing the two head to head rather than switching? The Snag and Pastel comparison answers the questions people ask most.

Where these details come from

Every Pastel detail behind this page is sourced and dated on the page where we cite each Pastel claim — each claim links to the Pastel page we read it on, with the date we read it. Something out of date? Email admin@dvcllc.io and we will fix it.