Claude in Chrome: inspect a browser-controlled lesson workflow

Connect the extension to a specific task

The March video introduces a Claude Chrome extension that operates websites through browser actions, including sites without an API. Luke uses his Skool community to demonstrate writing and publishing lessons. That is the recorded task, not a general authorisation to publish new material under another account.

Installation begins at 0:48 and model selection at 1:38. The description strongly favours Opus 4.6, calls the extension beta and describes limitations. Keep those as the recording’s context, rather than a current model recommendation or a claim that browser control is the only available approach today.

1. Follow the installation and model-selection sections.
2. Open the intended page and verify the account and destination.
3. Describe the lesson edit and the point at which its content should be reviewed.

Choose how the agent may proceed

Auto mode, ask-first mode and teaching workflows appear at 2:24. The distinction matters when a task moves from reading or drafting to making a public change. Choose the mode and review points deliberately so the agent’s next action is understandable.

The Skool test starts at 3:20. Watch how the work moves through the actual page and inspect the lesson content, formatting and destination. A completed text entry and a published lesson are different states of the workflow.

1. Specify the task and the actions it includes before starting.
2. Inspect the drafted lesson before any intended publication step.
3. Check the saved page state after an edit instead of relying only on the agent’s completion message.

Use the failure sections as practical evidence

The navigation section at 4:38 shows helping Claude stay on track. A Markdown-related technique follows at 5:14, then editing at 5:50 and crashes and tab quirks at 6:36. The description does not spell out the exact Markdown procedure; follow that recorded segment for the actual example.

Inspect the active tab and the last saved lesson state when the browser stalls or changes context. Keep unfinished work separate from the successful edits you can verify. The original scripting resource is https://ailuke.short.gy/HGFXXn-LMG82. The value of the demonstration includes its rough edges as well as its visible browser actions.

The takeaway

Judge browser automation by the correct page and saved edit, with explicit review at the point where the task becomes a public change.