Our extensions now install in one click

PageToVid films the real site in a real browser. That works beautifully for a public page, and stops at the first sign-in screen, the first step that needs a click in the right order, the first view that only exists once you have opened something.

Those are often the moments a product is proudest of. So we built two extensions, each doing what its environment does best, and they reach exactly the places a public crawler cannot.

In VS Code, the studio writes a project's capture plan: flows made of a real address and scripted steps, each with a label and a rough duration. It also sets up a starter pack for Claude Code, with the connection to PageToVid and slash commands for films, shows, formats, how-tos and assets.

Your API key never lands in a file. The extension keeps it in VS Code's secure storage and hands it to the editor's terminals, so the configuration only refers to a variable.

In Chrome, the extension replays those flows one click at a time and records each step as its own scene. It is also how a signed-in page gets filmed: you register a capture session from your own browser, and nobody ever types a password into PageToVid.

A store does not accept a package just because it works. It asks for clarity, and the work to get there was short but precise:

• Chrome 2.9.3: a store description of at most 132 characters, which means saying what the extension does in one sentence.
• VS Code 0.8.2: a proper licence file, a clean manifest, and the AI category, so people browsing for AI tools can find it.
• Both: the downloadable zip and .vsix rebuilt from the very same sources the stores received.

That last point matters to us. Whether you install from a store or from our site, you get the same extension, byte for byte.

The VS Code studio was published this morning as pagetovid.pagetovid-capture, and the Marketplace validated it the same day. Our site now shows two buttons in place of the download link: one to the Marketplace listing, and one that opens VS Code straight on the install. The .vsix file stays as an offline option for teams that install extensions from files.

It sounds like a small change. A side-loaded extension asks you to trust a file, find a menu and accept a warning; a store button asks for one click, and the editor keeps the extension up to date afterwards. Every improvement we ship now reaches you without you lifting a finger.

The Chrome extension needs access to the pages it records, and it runs a small collector there to know where to click. An extension with that reach goes to the Web Store's in-depth review, and we think that is exactly right.

A careful review is part of what makes a store button trustworthy. Until the listing is public, the Chrome extension stays available from our site, and the switch to a store button will follow as soon as it is approved. You can already see how both fit into a workflow on the developers page and, for the editor side, on the VS Code page.

We had kept the extensions as files while they changed every week; it felt practical. Seen from the other side, it made every update a manual download and every install a small act of trust.

The stores remove both. The tools that film the hardest parts of a product are now as easy to get as any other extension, and they stay current on their own. That opens the signed-in, step-by-step part of a product to anyone who wants to show it, including from an assistant, as we describe on the assistants page.