CHAPTERS
- 0:00 – 1:01
Hands-free work: letting AI drive the browser and computer
Claire introduces the idea of “Look Ma, No Hands”: using AI to navigate websites and your computer when your hands (and attention) are busy. She previews three categories of examples—builder, productivity, and personal/fun use cases—powered by recent improvements in browser/computer control.
- •Motivation: reduce digital toil by delegating clicking/typing to AI
- •Browser/computer control has improved significantly in her experience (Codex + newer models)
- •Preview of upcoming demos: QA, productivity workflows, and personal tasks
- 1:01 – 1:31
Sponsor: Runway (creative platform for images/video/content)
A brief sponsorship segment explaining Runway as an end-to-end AI creative platform. Claire highlights speed from concept to deliverable and mentions enterprise adoption and a promo link/code.
- •Runway supports generating images, video, and creative deliverables
- •Positioned as fast and scalable for teams without ballooning budgets/timelines
- •Mentions notable customers/studios and the promo URL/code
- 1:31 – 3:02
Browser use vs. AI-native browsers—and why Claire picks Codex
Claire defines what “browser use” and “computer use” are: LLMs controlling mouse/keyboard to operate apps and websites. She contrasts this with AI-native browsers and explains why Codex (ChatGPT desktop app + extension) feels best for reliable computer control.
- •LLMs can control mouse/keyboard to operate your machine like a “virtual coworker”
- •AI-native browsers exist (e.g., Comet/Atlas), but she prefers using tools via Codex/Claude
- •Codex is framed as the most capable at full computer control in her workflow
- 3:02 – 4:02
Setup and invocation: desktop app + Chrome extension, plus @browser/@chrome/@computer
She explains the practical setup: install the desktop app and the official Chrome extension to enable control. Then she breaks down the three invocation modes in Codex—side-browser, Chrome-control, or full-computer control—and how choosing the right use case is the real key.
- •Requirements: desktop app installed + official Chrome extension in Chrome
- •Three control modes: @browser (side window), @chrome (controls Chrome), @computer (whole machine)
- •Success depends on selecting strong use cases for delegation
- 4:02 – 6:34
Use case #1: AI-driven QA of a web onboarding flow (desktop + mobile)
Claire demonstrates using browser control as a QA companion for a product onboarding flow. She asks the agent to test usability and mobile responsiveness, take screenshots, and log issues into a Google Sheet—mirroring how a thorough human tester would work, but more exhaustively.
- •Delegating manual UI QA to an agent for usability and responsiveness checks
- •Agent clicks through flows, tries dropdowns, error states, and viewport resizing
- •Goal output: screenshots + structured issue list in a Google Sheet
- 6:34 – 9:05
QA philosophy: exhaustive edge cases and the power of under-prompting
While the agent runs, Claire explains why this approach beats her typical “happy path” testing. She notes that newer frontier models often perform better with minimal instruction, planning their own coverage rather than following an overly prescriptive checklist.
- •Humans tend to test the happy path; agents can systematically probe failure states
- •Exhaustiveness: tries alternate paths (team vs. individual), required fields, and errors
- •Tip: under-prompt newer models for better autonomous planning and coverage
- 9:05 – 12:08
QA results: 11 issues found, including a high-severity blocker—with a screenshot-backed spreadsheet
The run surfaces a blocking validation problem and additional issues across desktop and mobile. Claire shows the resulting Google Sheet: prioritized findings, reproduction steps, remediation notes, viewport context, and embedded screenshots for tracking fixes and delegating follow-up work.
- •Finds a key bug: Continue clickable without required selection/validation (blocker)
- •Completes mobile testing and flags UI/UX issues (overflow, touch targets, accessibility cues)
- •Outputs a practical Google Sheet with steps, severity, and screenshots for each issue
- 12:08 – 16:10
Use case #2: Persona testing your product with agent “fresh eyes”
Claire shares a persona-driven testing workflow suggested by her husband: have the agent use the product as distinct user types, then write a research-style critique. The personas include a PM creating a PRD, an engineer turning it into a technical spec/prototype, and a team leader assessing adoption.
- •Prompting the agent to behave like multiple personas while navigating the app
- •Three personas: PM (create PRD fast), engineer (tech spec/prototype), team leader (usage oversight)
- •Deliverable: critique with friction points, delight moments, and improvement ideas
- 16:10 – 18:11
Persona test findings: handoff friction, missing cross-reference patterns, and unclear loading/error states
As the agent transitions from PM to engineer, it reveals a key product friction: difficulty referencing one created document in another thread. The run also surfaces UX feedback around slow/opaque loading and unclear system status during generation, especially when errors occur.
- •Persona handoff exposes structural expectation gaps (document referencing/mentioning)
- •Agent behavior highlights what a new user assumes will work vs. what actually works
- •Feedback includes loading transparency, performance perception, and failure-state clarity
- 18:11 – 20:42
Use case #3: LinkedIn inbox triage and drafting replies without an official API
Claire shows a hands-free workflow for processing LinkedIn DMs: prioritize critical messages, draft friendly replies for simple notes, and leave guidance for the rest. She notes this is useful because LinkedIn lacks a convenient official API/MCP workflow, and she adjusts model “effort” for speed vs. quality.
- •Automates inbox triage: respond to critical items, annotate others with suggested replies
- •Works around lack of official LinkedIn integrations by using browser control
- •Model calibration: lower effort/faster models may be sufficient for routine replies
- 20:42 – 23:43
Use case #4: AI personal shopper in Chrome (with human verification when challenged)
Using @chrome, Claire asks the agent to shop Free People’s sale for Hawaii-appropriate, breastfeeding-friendly items and add 10 options to her cart without checking out. The demo highlights both the convenience and real-world friction like bot/agent verification steps where the human must intervene.
- •Shopping prompt constraints: size medium, comfort, nursing-friendly, Hawaii weather
- •Agent navigates sale pages, selects items, and populates the cart automatically
- •Caveat: bot checks/verification can require the human to step in as the “hands”
- 23:43 – 26:16
Rapid-fire additional uses: forms, controlling your phone via mirroring, remote router fixes, and creating Docs/Sheets via the browser
Claire closes with practical miscellaneous scenarios where computer use shines: filling tedious forms, operating an iPhone through Mac mirroring, and handling remote network/router tasks while out of state. She also notes that when plug-ins/MCPs fail, letting the agent do the task directly in the browser can be the most reliable path.
- •Automate painful form-filling (procurement, camps, legacy websites)
- •Use iPhone mirroring + computer control to operate phone apps from the desktop
- •Remote ops story: adjusting router/firewall settings, SSH access, then closing ports
- •Fallback tactic: create Google Docs/Sheets directly via browser when integrations fail
- 26:16 – 27:40
Wrap-up: why computer use changes digital life (and a call for privacy/security questions)
Claire reflects on the arc from QA debugging to personal shopping, arguing that AI-driven computer control will reshape how we interact with digital systems. She invites viewers to share their own use cases and asks for questions about privacy and security for future coverage.
- •Computer use reduces time-on-keyboard and enables work to happen in the background
- •Framing: a major shift in human-computer interaction
- •Invites comments: use cases plus privacy/security concerns and follow-up topics
