The Article-to-Video Pipeline — How We Automate Video Creation With Claude in Chrome

This pipeline exists because a popular browser-based AI notebook tool generates high-quality cinematic videos from written content — but it has no API. The only way to operate it programmatically is through the browser UI. Claude in Chrome is the bridge.

What follows is documentation of a running production pipeline, including the failure modes that actually occur and how they’re handled.

The Architecture: Two Scheduled Tasks

The pipeline runs as two complementary Cowork scheduled tasks, staggered 30 minutes apart on the same 3-hour cycle.

Task 1 — Kickoff (runs at :00 on each scheduled hour)

1. Calls the WordPress REST API to fetch recently published articles
2. Checks the pipeline log (a Notion page) for articles already processed
3. Selects one unprocessed article per run
4. Uses Claude in Chrome to open the notebook tool in the browser
5. Creates a new notebook, adds the article URL as a source
6. Navigates to the video generation interface and triggers Cinematic generation
7. Logs the article as “processing” in Notion with the notebook URL and timestamp

Task 2 — Harvest (runs at :30 on each scheduled hour)

1. Reads the Notion pipeline log for articles in “processing” status
2. Filters for any that were kicked off more than 25 minutes ago
3. Uses Claude in Chrome to open each notebook and check if the video is ready
4. If ready: downloads the video file via Chrome
5. Uploads the video to the WordPress media library via REST API
6. Creates a draft watch page post with the embedded video, article summary, and schema markup
7. Updates the Notion log to “completed”

The Account Rotation Layer

Browser-based AI notebook tools typically impose daily limits on cinematic video generation per account. One account isn’t enough to process a continuous stream of articles.

The pipeline handles this by rotating between two accounts. When the primary account hits its daily generation limit, the kickoff task switches to the secondary account. Both accounts have the notebook tool open in different Chrome profiles, with the extension installed in each.

There’s also a notebook count limit per account. Old notebooks that have already been harvested get deleted periodically to stay under the cap.

The Failure Modes — Documented From Production

This is the part that most automation write-ups skip. Here are the real failure modes this pipeline encounters, in roughly descending frequency:

Timeout (Most Common)

Video generation on the notebook tool can take anywhere from 25 minutes to several hours, depending on server load. The harvest task has a 3-hour timeout window — if a video hasn’t finished after 3 hours, it’s marked as failed and the article is available for retry. In practice, a meaningful portion of generation runs take longer than the timeout window, especially during peak hours.

Mitigation: failed articles are automatically available for re-kickoff in the next cycle.

Chrome Tab Closure

If the Chrome tab that Claude in Chrome is operating gets closed — by the user, by a browser crash, or by an accidental window close — Claude loses access and the harvest fails. The video may be ready in the notebook tool, but there’s no way to download it without re-establishing the browser connection.

Mitigation: the pipeline marks the article as failed. Manual recovery: reopen the notebook tool in the correct Chrome profile, reinstall the extension if needed, and re-run the harvest for that article.

Daily Generation Limits

Both accounts can hit their daily cinematic generation limit on high-volume days. When this happens, the kickoff task will fail to start new videos until the limit resets — which happens on a daily cycle. The pipeline logs these failures with a clear reason so they’re easy to spot.

Mitigation: add a third account if volume consistently exceeds two accounts’ daily limits.

Notebook Count Limits

Notebook tools cap how many notebooks a single account can hold. When an account is at its limit, new notebook creation fails. Regular deletion of completed notebooks (those that have been harvested) keeps the account under the cap.

What the Watch Page Looks Like

After a successful harvest, the pipeline creates a draft WordPress post with:

• The embedded video (hosted in the WordPress media library, not on an external service)
• A summary of the source article
• Chapter/segment markers if the tool generates them
• Article schema markup
• A link back to the original article

The post goes up as a draft, not published directly. A manual review step before publishing is intentional — the pipeline produces a lot of content, and a spot check catches cases where generation quality was unexpectedly low.

Why This Is Genuinely Novel

The combination of Cowork scheduling + Claude in Chrome + a browser-based tool with no API is a pattern that isn’t widely documented. Most automation examples assume APIs exist. This one doesn’t — it treats the browser UI as the API, and Claude in Chrome as the adapter layer.

The practical result: a pipeline that runs on a schedule, processes a backlog of articles at a rate of one per run, handles account rotation automatically, logs its own state, and surfaces failures with enough detail to recover from them manually.

The tools involved are off-the-shelf. What makes it work is the architecture.

Frequently Asked Questions