Model-free replay for repetitive browser automation flows

What to build

A browser-extension/desktop tool for solo builders and agencies that records a repetitive browser workflow once using an AI model, turns the recorded values into reusable input fields, then replays it deterministically on a schedule with no further model calls, auto-flagging only broken steps back to AI for repair.

Ops teams and indie hackers running repetitive browser tasks (data entry, scraping, form-filling) are paying per-run for always-on AI browser agents when most of the workflow is identical each time; a record-once, replay-deterministically tool can cut that cost to near zero while keeping an AI fallback only for the step that breaks.

Demand

Solo builders and small ops/agency teams currently running model-driven browser agents for repetitive tasks want this now because per-run inference costs scale linearly with volume, and r/nocode engagement on a 'record once, replay without AI' post shows practitioners are actively comparing scripted vs. AI-driven browser automation.

• r/nocodeEngagement

  Reddit thread 'Record once, replay without AI: what I learned making browser flows that don't need a model' — practitioner discussion noting most AI browser-agent requests are repetitive tasks that don't need a model on every run.

• Signal cluster (tech blog post)News

  Author describes building and learning from a record-once, replay-without-AI browser flow tool, implying firsthand practitioner experience with the cost/reliability tradeoffs of AI-driven browser automation.

• Opportunity brief (derived)Analysis

  Opportunity framing specifies target users (ops teams, agencies, indie hackers) who pay per-run for model-driven browser agents, suggesting observed market pain around recurring AI inference costs for repetitive browser tasks.

Stack

• Playwright
• Chrome Extension APIs
• OpenAI API or Claude API (for initial capture + step repair)
• Supabase (flow storage/auth)
• node-cron or a hosted scheduler
• Stripe (usage-based billing)

Solo + AI difficulty

The deterministic replay engine (record selectors/values, parameterize fields, step through on a schedule) is a well-scoped Playwright project buildable in 2-4 weeks solo with AI assistance; the hard part is the graceful-degradation layer that detects a broken step, isolates it, and hands only that step back to a model for repair without re-running the whole flow or over-triggering false failures.

Entry threshold

A solo developer can build an MVP in a few weeks on top of existing browser automation primitives (Playwright/Puppeteer) plus a thin AI layer for initial recording and failure repair; main effort is UX around step-editing and failure recovery, not novel infrastructure.

Window

6-12 months

Where to find first users

• r/nocode
• r/sysadmin or r/automation
• Product Hunt launch
• indie hacker communities (IndieHackers.com, Twitter/X build-in-public)

Competitors

• Browser Use
• Skyvern
• UI.Vision
• Axiom.ai

Counter-signals & risks

• Deterministic replay is brittle to site/UI changes (selectors, layout, flow branching) in ways that a model-driven agent can adapt to in real time, potentially increasing maintenance burden despite the 'graceful degradation' fallback.

• The addressable market of solo builders and small teams doing repetitive browser automation may be too small or too price-sensitive to sustain a standalone product versus being a feature bolted onto existing RPA or browser-agent platforms.

• Mandatory human approval for money/data-sending steps, while safer, reduces the 'fully automated' value proposition and may push time-sensitive or high-volume use cases back toward fully AI-driven or traditional RPA tools.