Build Web Automations via Demonstration
Details
- External ID
- 46779864
- Source
- HN
- Company
- —
- Product
- Build Web Automations via Demonstration
- Website domain
- notte.cc
- Launched
- Jan. 27, 2026
- Cohort
- —
- Upvotes
- 36
- Upvotes percentile
- 0.7424242424242424
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
Hey HN,We’ve been building browser agents for a while. In production, we kept converging on the same pattern: deterministic scripts for the happy path, agents only for edge cases. So we built Demonstrate Mode.The idea is simple: You perform your workflow once in a remote browser. Notte records the interactions and generates deterministic automation code.How it works: - Record clicks, inputs, navigations in a cloud browser - Compile them into deterministic code (no LLM at runtime) - Run and deploy on managed browser infrastructureClosest analog is Playwright codegen but: - Infrastructure is handled (remote browsers, proxies, auth state) - Code runs in a deployable runtime with logs, retries, and optional agent fallbackAgents are great for prototyping and dynamic steps, but for production we usually want versioned code and predictable cost/behavior. Happy to dive into implementation details in the comments.Demo: https://www.loom.com/share/f83cb83ecd5e48188dd9741724cde49a-- Andrea & Lucas, Notte Founders
Enrichment
- Theme
- browser automation and scraping for AI
- Vertical
- Horizontal
- Function
- Workflow automation
- Audience
- B2B
- AI stance
- AI-native
- Project type
- Commercial product
- Normalized one-liner
- web automation by demonstration
- Manually corrected
- False
Could you build this?
Partial Capturing browser DOM events and translating them to Playwright/Puppeteer scripts is achievable, but cloud sandboxing and resilient locator synthesis require dedicated browser infrastructure engineering.
What it would actually take: The architecture combines a headless remote browser stream (WebRTC/CDP) with a client-side recorder that hooks into input and DOM mutation events. The challenging piece is synthesizing resilient element selectors and self-healing automation logic that doesn't break when DOM trees mutate, requiring strong browser automation and distributed remote container infrastructure.
Discussion
20 comments analyzed.
Competitors mentioned: Playwright, BrowserUse, Browserbase, BrowserBook, Skyvern
Concerns raised: Crowded market with many similar startups, Browser automation space already saturated even within YC, Open source alternatives would be more trustworthy
Feature requests: AI agent to explore product as target user and test/break things, Shared automated scripts for first-time users to execute sample workflows
Competitors
Other products that read as similar to this one — 108 launches clear the similarity bar, closest 8 shown.
Attention rank: #32 of 109 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 87 days after the earliest competitor.
- Libretto · hn · 2026-04-15 · 134 upvotes · similarity 0.48
- Anything API · hn · 2026-03-12 · 5 upvotes · similarity 0.47
- Tabstack Browser Automation · ph · 2026-07-01 · 387 upvotes · similarity 0.46
- Webctl · hn · 2026-01-14 · 134 upvotes · similarity 0.45
- BrowserAct · ph · 2026-06-25 · 561 upvotes · similarity 0.44
- Browser4 · hn · 2025-12-13 · 7 upvotes · similarity 0.42
- AI Subroutines · hn · 2026-04-17 · 46 upvotes · similarity 0.40
- ActBrow · ph · 2026-09-24 · 2 upvotes · similarity 0.39
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a workflow automation tool for Real estate yet.