SLIDESHOT [docs] Markdown
For agents: read the markdown version of these docs →

Claude Code & Cowork setup

This page covers two Anthropic products that have different best paths into Slideshot:

  • Claude Code is the terminal-based developer agent. Users typically have Node, npx, and shell access available, so the CLI is the simplest path and the skill teaches Claude Code how to drive it.
  • Cowork is the consumer and work app from Anthropic. Users do not always have a shell, so the recommended path is to install Slideshot as a plugin from the plugin marketplace and let Cowork call the MCP server.

Pick the section that matches the product you are using.

Claude Code

The fastest setup is: install the Slideshot skill, then call the CLI through npx. The MCP server is also supported if you want Claude Code to manage runs from the conversation without going through the shell.

Copy this into Claude Code

Paste this whole instruction into Claude Code and let it walk you through the rest.

You are helping me connect Slideshot to Claude Code.

1. Install the Slideshot skill with `npx skills install slideshot` (pick Claude
   Code from the detected agents). The skill teaches you how to plan a
   recording, choose run options, and handle paused runs that ask for OTP.
2. Confirm `SLIDESHOT_API_KEY` is set in my shell. If not, ask me to export it.
3. Optionally, register the Slideshot MCP server at https://api.slideshot.ai/mcp
   if I want you to manage runs from the conversation instead of the CLI.
4. Run one small test recording against a public URL using `npx slideshot runs
   create <url> --goal "..."` and download `demo.mp4` when the run succeeds.

Do not print my API key or any credential back to me, and do not store
secrets in the repo.

1. Install the skill

npx skills install slideshot

Pick Claude Code from the list of detected agents. The installer drops the skill into ~/.claude/skills/slideshot/. Re-run the same command to update.

2. Set your API key

The CLI reads SLIDESHOT_API_KEY from the environment:

export SLIDESHOT_API_KEY="sk_live_xxxx"

Persist it in your shell profile so every Claude Code session picks it up.

3. Use the CLI

Run any CLI command through npx:

npx slideshot runs create https://app.example.com \
  --goal "Open the analytics dashboard and create a new project"

npx slideshot runs wait <RUN_ID>
npx slideshot runs download <RUN_ID> --artifact demo.mp4 --dir ./artifacts

4. (Optional) Add the MCP server

If you want Claude Code to manage runs without shelling out, register the MCP server:

claude mcp add slideshot --transport http https://api.slideshot.ai/mcp

The first request opens an OAuth approval page in your browser. After approval, the Slideshot tools (create_run, get_run, list_runs, submit_run_input, cancel_run, list_run_artifacts, credential management, submit_feedback, fetch_brand) become available in the conversation.

Test the setup

Ask Claude Code to create a small recording:

Create a Slideshot recording of https://docs.slideshot.ai that shows the docs landing page and the getting-started section.

Claude Code will either call npx slideshot runs create (if you went the CLI path) or create_run via MCP, poll the run, and download demo.mp4 when it succeeds.

Troubleshooting

  • npx slideshot fails with 401. Make sure SLIDESHOT_API_KEY is exported in the shell Claude Code is running commands in.
  • Skill not appearing in Claude Code. Re-run npx skills install slideshot and restart Claude Code so it re-reads ~/.claude/skills/.
  • MCP OAuth approval did not redirect back. Re-run claude mcp add and make sure the redirect URI Claude Code provides is reachable from your browser.
  • Run paused with awaiting_input. Read the awaiting_input.prompt and submit the value via npx slideshot runs input <id> --value <otp> or, on the MCP path, the submit_run_input tool. See Runs.
  • Recording stops at a login page. Save credentials for that domain first. See Login to any web app.

Cowork

The Cowork app does not run shell commands, but it supports plugins. Install the Slideshot plugin from the marketplace and Cowork can call Slideshot directly from the conversation through MCP.

1. Install the plugin

Open github.com/slideshot/skills and follow the README’s plugin install instructions. The repo doubles as the canonical plugin source for Cowork.

In Cowork, the install flow is:

  1. Open the plugins or extensions panel in the Cowork UI.
  2. Add the Slideshot plugin from the marketplace.
  3. Connect the Slideshot MCP server when Cowork prompts you.
  4. Approve the OAuth consent page that opens in your browser.

After approval, the Slideshot tools appear in the conversation: create_run, get_run, list_runs, submit_run_input, cancel_run, list_run_artifacts, credential management, submit_feedback, and fetch_brand.

2. Test the setup

Ask Cowork to record a small workflow:

Record a Slideshot demo of https://docs.slideshot.ai that shows the docs landing page and the getting-started section.

Cowork calls create_run, polls get_run until status is succeeded, lists artifacts with list_run_artifacts, and shares the demo.mp4 download link.

Troubleshooting

  • Plugin install does not finish. Refresh the Cowork marketplace and retry. The plugin URL is the same as the skills repo.
  • MCP OAuth approval failed. Re-run the connect step from Cowork’s plugin panel.
  • Tool calls fail with 401. Reconnect the plugin so Cowork refreshes its access token.
  • Run paused with awaiting_input. Tell Cowork to read the prompt and submit the value via submit_run_input. See Runs.
  • Recording stops at a login page. Ask Cowork to save target-app credentials first. See Login to any web app.