Canvas Capture Extension
Rebuild, install, and reload the private Remotion Canvas Capture unpacked Chrome extension. Use when the extension needs to be restored after a Codex worktree was deleted, rebuilt after source changes, moved to its durable install directory, or reloaded in Chrome or Chrome Canary.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Canvas Capture Extension when an AI agent needs a reusable SKILL.md workflow for this job: Rebuild, install, and reload the private Remotion Canvas Capture unpacked Chrome extension. Use when the extension needs to be restored after a Codex worktree was deleted, rebuilt after source changes, moved to its durable install directory, or reloaded in Chrome or Chrome Canary.
When not to use it
Skip Canvas Capture Extension when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/canvas-capture-extension # Save SKILL.md to ~/.claude/skills/canvas-capture-extension/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/canvas-capture-extension/SKILL.md. For a shared project, commit the folder at .claude/skills/canvas-capture-extension/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Canvas Capture Extension skill for this task: Use Canvas Capture Extension when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Canvas Capture Extension
Build the extension from `packages/canvas-capture-extension`, but always install the unpacked copy outside the checkout so deleting a worktree cannot break it.
## Rebuild and install
1. Locate a Remotion checkout containing `packages/canvas-capture-extension/package.json`. Prefer the current checkout; otherwise use `/Users/jonathanburger/remotion`. 2. Run:
```bash .agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh \ --repo <remotion-checkout> ```
The script builds with Bun and installs the complete WXT bundle in `/Users/jonathanburger/Applications/Remotion Canvas Capture Extension`. Building does not require an installed browser. To use the extension, choose Chrome 157.0.8080.0 or newer with Canvas Draw Element enabled.
3. Confirm that the installed directory contains `manifest.json`, `background.js`, `capture.js`, `drag-image.js`, `shot-tools.js`, `logo.svg`, and the generated extension icons.
## Develop with React and Vite
1. Close any running Recorder Chrome instance that uses the dedicated Canvas Capture profile. 2. From `packages/canvas-capture-extension`, run `bun run dev`. 3. WXT writes the development bundle to the durable directory `/Users/jonathanburger/Applications/Remotion Canvas Capture Extension Dev`, launches Chrome for Testing with the Canvas Draw Element feature enabled, and loads the extension automatically. 4. Click the extension icon to show the in-page controls. Source and manifest changes cause WXT to rebuild and reload the affected extension contexts.
Use the separate development directory only for `bun run dev`. Continue using the production install directory above for manually loaded builds.
The Remotion pages receive recordings through `externally_connectable` messaging; the extension does not inject a receiver content script. To test a local destination, set `CANVAS_CAPTURE_HANDOFF_ORIGIN` (for example `http://localhost:3000`) when running `bun run dev`. Production builds always use `https://www.remotion.dev`.
To select another Chrome 157.0.8080.0 or newer browser, set `CANVAS_CAPTURE_BROWSER_EXECUTABLE` to its executable path when running `bun run dev`. Development uses the version-neutral `~/Library/Application Support/Remotion Canvas Capture` profile.
## Reload in Chrome
- Launch Chrome 157.0.8080.0 or newer with the dedicated Canvas Capture profile, then open `chrome://extensions`. - Enable **Developer mode** on `chrome://extensions`. - If **Remotion Canvas Capture** already points to the durable directory, click **Reload**. - If Chrome shows the deleted worktree path, remove that broken entry, choose **Load unpacked**, and select:
```text /Users/jonathanburger/Applications/Remotion Canvas Capture Extension ```
This one-time move changes the extension ID because Chrome derives unpacked extension identity from its absolute path.
- Keep loading future production builds from the durable install directory, never from a worktree-local `dist` directory. WXT-managed development builds use the separate durable development directory documented above. - Enable `chrome://flags/#canvas-draw-element` and restart Chrome when the experimental HTML-in-canvas API is unavailable. Alternatively, launch with `--enable-features=CanvasDrawElement`; either method is sufficient. Do not add `--enable-blink-features=CanvasDrawElement`, which triggers Chrome's unsupported-command-line warning.
Do not edit Chrome's `Preferences` or `Secure Preferences` files to move or reload the extension. Use Chrome's extensions page so its integrity metadata stays valid. Browser UI automation is allowed for loading, reloading, and activating Canvas Capture; do not require the user to perform those clicks.
## Prepare a shot
Open the requested webpage in the compatible recording browser and activate Canvas Capture through its toolbar icon or the Extensions menu. This exposes the `setup_shot`, `get_shot`, and `save_recording` WebMCP tools in that tab.
Prepare the page and viewport, call `setup_shot`, and inspect a still preview with `get_shot`. Leave the browser open with the shot ready for the user to record. Start and stop recording manually so the user controls cursor movement.
Intended uses
- Use Canvas Capture Extension when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.