Skip to main content
Someone on your team records the checkout page failing and sends you https://jam.dev/c/abc123. Paste it to your coding agent and it starts from what happened, not from a guess. Nobody writes a repro or scrubs a video.
Install the CLI and run jam skills install first. See Get started.

​
Ask your agent

The jam-cli skill tells the agent which reads to run and in what order. The steps below show the commands it runs, so you can run them yourself too.

​
What the agent runs

1

Read the errors and failed requests

The network read returns one line: POST /api/checkout answered 500 at 42 seconds. The console read returns the TypeError the page threw a moment later. Add --json to get the response body and the stack trace.
2

Look at the screen when the logs run out

This writes a JPG of the page at 42 seconds: the card field filled, the button grayed out. Logs say what broke. Frames say what the person saw.
3

Fix the code

With the endpoint, the payload, and the stack trace, the agent finds the handler and patches it.
4

Comment the fix on the Jam

--at pins the comment to the moment of failure. The reporter sees it on the Sharepage.

​
Next