jam record records the screen while a check runs, uploads it, and prints a Jam link. Put that link on the pull request.
jam record runs on macOS and Linux. Install the CLI and run jam skills install first. See Get started. Run jam doctor to check that recording works on your machine.Ask your agent
show me, prove, and record tell the agent to use the jam-proof skill. It picks what to record, records the check, and hands back the link.
Pick what to record
Pick the first option that shows the change. Each one further down puts more of your machine in the video.
Whenever the target is a browser, add
--cdp, also when you pass a window or display flag. The Jam then carries the browser’s console logs and network requests next to the video, so a reviewer can check the request that used to fail. Without --cdp, the Jam is video only.
Record a command
Start a browser with a debug port, then wrap the check injam record run. The recording stops when the command exits.
--cdp points at. A check that launches its own browser runs out of view: the video shows the agent-browser page, and the Jam has none of the check’s console or network. The CLI passes the recorder’s address to the wrapped command in JAM_CDP_PROXY. Connect the check there, and its clicks and typing also show up as user actions in the Jam:
e2e/checkout.ts
Record steps you run yourself
When there is no single command to wrap, bracket the steps:jam record status to check the recording without stopping it. Run jam record cancel instead of stop to throw it away without uploading.
Make it readable
- Make the title the claim: “Deep link scrolls to comment 6”, not “proof”.
- Start from a known state. Reload the page or restart the app first.
- Keep it short. Thirty seconds that show the change beat five minutes.
Next
- For every
jam recordflag, receipt field, and status, see Record a window or the desktop. - To record tests in CI, follow Record end-to-end tests.