An MCP server and a CLI for any coding agent

Stop imagining what a pull request does. Watch it work.

A UI change arrives as a diff and two screenshots, and you play the rest in your head. With Grip, your coding agent records every change it ships, polished, and links it in the pull request.

Paste into your agent

Read https://bestboy.dev/grip/agents.md and record a demo of this change.

Or add it to Claude CodeCodexCursorOpenCodeVS CodeGemini CLI

macOS 15 or later on Apple silicon Free and open source Any MCP client

Today screenshots

feat(deployments): deploy from the list #482

Open Opened by an agent 2 days ago +412 −38

Adds a Deploy button. New deploys appear at the top and update live until Ready.

Before
After

anaruiz requested changes

Does Deploy lock while it runs? What does the new row show before it’s Ready? I’ll pull the branch and click through it.

Waiting on review for 2 days

With Grip recorded by the agent

feat(deployments): deploy from the list #482

Merged Opened by an agent 9 minutes ago +412 −38

Adds a Deploy button. New deploys appear at the top and update live until Ready.

anaruiz approved

Watched it. The button locks and the row builds in place. Ship it.

Merged 9 minutes after it opened

The same pull request. One you imagine, one you watch.

The problem

Your team ships more than anyone can read. Review is the slow part now.

Agents open pull requests all day. Each one is a diff, a summary the agent wrote, and maybe a screenshot. To know a UI change works, someone still pulls the branch and clicks through it.

  • A screenshot is one frame

    Loading, hover, empty, and error states live between the screenshots. That is where the bugs are.

  • Before and after skip the during

    Motion, focus, and timing exist only while the change runs. No still can show them.

  • Nobody records the video

    Recording, trimming, and uploading take longer than the fix did, so the video never gets made.

How it works

The presentation layer, automated. Every change ships with its video.

Your agent already knows what it changed, so it knows what to click. It hands Grip the steps in one tool call, and Grip records and polishes the video with no model in the loop.

  1. Your agent writes the steps

    Open the page, click Deploy, wait for Ready. The same selectors its tests already use.

  2. Grip plays and polishes them

    In a hidden window, at a human pace. It zooms where each click lands, glides the cursor, and marks each step.

  3. The video lands in the pull request

    An MP4, a GIF, and a share link, with one frame per step that your agent checks before it posts.

One tool call

It zooms where your agent clicks.

An agent’s clicks never move your real cursor, so a screen recording of them has nothing to follow. Grip makes each click itself, so it knows where every one lands.

Every agent tool
  • No Screen Recording permission
  • Your screen stays free while it records
  • A failed step stops the demo and names it
record_demo({
  "url": "http://localhost:3000/deployments",
  "title": "Deploy from the list",
  "steps": [
    { "click": "text=Deploy", "say": "Deploy from the list" },
    { "wait": "text=Building" },
    { "wait": "text=Ready", "say": "It updates live" }
  ],
  "share": true
})
{
  "state": "done",
  "seconds": 4.3,
  "steps": [
    { "index": 1, "label": "Deploy from the list", "ok": true },
    { "index": 2, "label": "wait text=Building", "ok": true },
    { "index": 3, "label": "It updates live", "ok": true }
  ],
  "mp4": "~/Desktop/Deploy from the list.mp4",
  "gif": "~/Desktop/Deploy from the list.gif",
  "link": "https://bestboy.dev/v/x7Kq2mP9aB3c"
}
One link

One link for the whole team. Wherever they already work.

Not everyone reads GitHub. The link plays in any browser, so design, product, and support see what changed without the branch.

  • In the pull request

    Under a Demo heading at the top of the description, where the reviewer starts reading.

  • In the issue and the channel

    Linear and Slack show its poster and title, so people know what they are about to watch.

  • Private when it has to be

    A private link plays only for your team, or for someone you send its key to.

The review loop

Your team comments on the frame. Your agent answers.

Teammates comment on the exact moment and spot in the video. Your agent reads every thread through Grip, fixes the code, records the fix behind the same link, and replies on each one.

How your agent reads feedback
  • Guests comment without an account
  • Each thread keeps its moment and spot
  • A reply can resolve its thread

~/acme/storefront

› Read the feedback on bestboy.dev/v/x7Kq2mP9aB3c and fix it.

● get_feedback
  └ 3 open threads
    0:01  anaruiz   Deploy should lock while it runs
    0:03  mayachen  The new row jumps when it turns Ready
    0:04  guest     Can the row show the commit message?
● Fixed 3 threads in app/deployments/list.tsx
● record_demo  ✓ ✓ ✓ ✓  4.6 s
  └ version 2 of bestboy.dev/v/x7Kq2mP9aB3c
● reply_feedback  3 replies, 3 resolved
Set up

One paste. Your agent does the rest.

Your agent reads one Markdown file. It installs Grip if it is missing, adds Grip to its own tools, and records a demo to prove it works.

What your agent does

~/acme/storefront

› Read https://bestboy.dev/grip/agents.md and record a demo of this change.

● Fetch bestboy.dev/grip/agents.md
● Grip is not installed. Installing it in /Applications
  └ Grip.app, signed and notarized
● claude mcp add --scope user grip -- /Applications/Grip.app/…/grip-mcp
  └ Grip’s tools load in the next session. This demo uses its CLI.
● grip record_demo < demo.json
  └ ✓ click Deploy  ✓ wait Building  ✓ wait Ready  4.3 s
  └ bestboy.dev/v/x7Kq2mP9aB3c
● Added the demo to pull request #482.

Or add it yourself

claude mcp add --scope user grip -- /Applications/Grip.app/Contents/Resources/grip-mcp

Needs Grip in Applications. Download for macOS

Good questions.

Another question? Ask on GitHub

Which apps can it record?

Any web page your agent can open: a dev server on localhost, a preview deployment, or production.

Does it take over my screen?

No. Grip plays the steps in a hidden window, so you keep working, and macOS never asks for Screen Recording.

How does the video get into the pull request?

Your agent puts the share link under a Demo heading at the top of the description. It plays in any browser, with no app to install.

Do I need an account?

Not to record: the MP4 and the GIF stay on your Mac. A share link signs in to bestboy.dev once.

Can teammates without an account comment?

Yes. Anyone who can open the link can comment as a guest, and your agent reads their comments too.

Can I change the video?

Yes. Each demo is a Grip project. Open it to cut, zoom, or add a voiceover, and export again.

Does it run in CI?

Not yet. Grip runs on macOS 15 or later on Apple silicon.

Is it free?

Yes. Grip is free and open source under AGPL-3.0, and viewers and comments never cost anything.

Ship the video with the change.

Paste one line into your agent. Its next pull request shows how the change works.

Paste into your agent

Read https://bestboy.dev/grip/agents.md and record a demo of this change.