Web pages as clean Markdown
Plainweb turns a URL into compact content for extraction, summarization, and downstream research.
DynamicThe web keeps moving.
Your agent needs more than one way through it.
Read with clean extraction, navigate with reusable site knowledge, and open a real browser only when the task requires interaction. The agent chooses a surface that matches the job.
https://supplier.example/portal/orders/1842
⋯Live browserClean extractionSite guidanceTask #1842 · running
SUPPLIER PORTALOrdersInventoryAccount
ORDER #1842
Confirm revised delivery
Dock availability changed. Select a new appointment window.
10:14:02 page ready10:14:04 option selected10:14:04 approval requested
Three surfaces.
One task contract.
Browser agents often use one expensive interaction loop for reading, navigation, and submission. That increases latency and exposes the agent to more untrusted page content than necessary. Pilot’s complementary web apps let a workflow begin with clean extraction, move to typed guidance, and open an interactive browser only for the steps that require it.
A real Chrome execution surface
Otto connects the agent to browser tabs for extraction, screenshots, and supported site interactions.
ReadableTask-specific site guidance
Bowmark stores concise navigation knowledge and improves it with feedback from completed workflows.
RepeatableWeb workflow routerRoute one brittle workflow
Route one brittle workflow
through the right web surface.
Give us the site and task. We will separate what should be extracted, what can follow known navigation, and what genuinely requires a live browser.
What you get
- 01Plainweb/Bowmark/Otto split
- 02Interaction boundary
- 03Proposed result artifact
Task trace
From intent to observable result.
A content question should not launch a browser. A known workflow should not rediscover the site. A genuine interaction can escalate to Chrome with the relevant context already assembled.
- 01
Read before opening a browser
Use clean extraction for content-only tasks and reduce unnecessary interaction.
- 02
Load task guidance
Apply a known site path when the destination and workflow are understood.
- 03
Escalate to Chrome
Use the interactive surface for forms, authenticated sessions, or visual state.
- 04
Capture what worked
Feed successful task knowledge back into a reusable navigation guide.
Technical basis
Specific product surfaces.
Inspectable in the docs.
- 01Clean URL-to-Markdown extraction
- 02Real Chrome extension and relay
- 03Screenshots and page extraction
- 04Reusable site-task guidance with feedback