Cuitty Pilot
AI-assisted browser automation.
Playwright core · AI-assisted selectorsrecord, replay, headless CI runsemits → observe, code, safe
Pilot run console
digitalocean.token.create
Interactive mode
Operators approve each breakpoint with the resolved selector, masked values, and a highlighted screenshot.
recording
00:58
video + trace + screenshots
Open provider dashboard
navigate · goto-dns
2approve
Resolve Add record button
click · open-add-record
3pending
Fill record fields
fill · fill-record
4pending
Save and capture result
capture · save
event stream
› step.awaiting_approval open-add-record
› operator sees screenshot highlight + selector
› approval required before destructive or credential steps
› edited selector can be persisted as a new playbook version
Breakpoint approval
selector: role=button[name=/generate new token/i]
ApproveEdit
Three operating modes
Record provider-dashboard workflows, replay them as deterministic Playwright playbooks, and let AI handle selector healing, bounded decisions, and review summaries. Pilot automates the dashboards that don't have APIs.
Failed playbook runs produce Video recordings for review. Every selector heal, replay, and assertion emits trace spans to Observe.
Pilot run console
digitalocean.token.create
Interactive mode
Operators approve each breakpoint with the resolved selector, masked values, and a highlighted screenshot.
recording
00:58
video + trace + screenshots
Open provider dashboard
navigate · goto-dns
2approve
Resolve Add record button
click · open-add-record
3pending
Fill record fields
fill · fill-record
4pending
Save and capture result
capture · save
event stream
› step.awaiting_approval open-add-record
› operator sees screenshot highlight + selector
› approval required before destructive or credential steps
› edited selector can be persisted as a new playbook version
Breakpoint approval
selector: role=button[name=/generate new token/i]
ApproveEdit
Keep the playbook beside the browser
Pilot playbooks are designed to make every captured step inspectable, parameterized, and reviewable. This interactive model shows how a future Cuitty Chrome client could keep recording and approval in context.
Cuitty Chrome · concept UI
Author a playbook where the work happens.
Simulated product concept — it neither installs a Chrome extension nor controls your browser.
CCuitty Pilotconcept
Ready to record a bounded workflow
3 captured steps
Ready to record a bounded workflow
Playbooks are the automation contract
Declarative .cuitty playbook data with Playwright execution.
Record workflows, refine with AI-ranked selectors and parameterized
inputs, and replay deterministically. Every run is audited and produces
a video artifact.
Record
Structured events and DOM snapshots captured from your browser session. No manual scripting.
Refine
AI-ranked selectors, parameterized inputs, and YAML-importable playbook format.
Trust
Replays are deterministic. Records emit audit events. Failed runs become fixable evidence with AI-proposed diffs.
Observe. Propose. Validate. Save.
When a provider dashboard changes, Pilot's AI bridge receives visible text, the accessibility tree, a screenshot, and the step's intent. It proposes a healed selector — you approve before it's saved. AI is used only for authoring and healing, never for execution.
1. Observe Detect stale selector
2. Propose AI suggests replacement
3. Validate Human reviews diff
4. Save Update playbook
Every run is recorded, secrets are redacted
Video, trace, network, console, and screenshots recorded per run. Secrets are redacted before persistence. SpiceDB-separated permissions ensure playbook access and execution rights are distinct.