DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to visit every search result and collect details from each with Vitre

Use forEach to open each result page on a lane pool and gather extracted fields in row order.

Authorization notice. Vitre is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Account pooling. Running many lanes against the same site may conflict with that site's terms, so check them before fanning out at volume.

Who it is forA developer building a price or listing monitor who needs detail data for each row a search page produced.

The problemOpening many pages one by one in a single WebView is slow, and parallel WebView calls race each other.

The outcomeA details variable holding one extracted record per item, in row order, with failed items recorded instead of stopping the run.

What you need first

  • Kotlin 2.3.10 Multiplatform project (Android minSdk 24, iOS 15.0+, or desktop with JetBrains Runtime and JCEF 21)
  • Maven Central access, which is the only setup needed for the published artifacts
  • Compose Multiplatform if you want the optional vitre-compose UI layer

Steps

  1. Extract the result rows with extractRows into a named variable such as results.
  2. Add forEach over that variable with an item name such as product and a limit.
  3. Inside the body, navigate to template("{product.url}"), waitFor the detail element, and add extract steps.
  4. Provide a LaneSource with more than one lane if you want items to run in parallel, then read the details variable from Completed.

Prompt for your agent

In <project-path>, build a Vitre workflow that extracts rows from <search-url> into results, then uses forEach to visit each row URL and extract <detail-selectors>. Expected output: a details array in row order with one entry per item. Verify that any failed item appears as a recorded failure rather than aborting the whole run.

Caveat. The README says a fan-out is a page barrier, so the step after forEach starts on a blank page with variables intact, and lanes must be configured in your own app.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for ggoggam/vitre and "Visit every search result and collect details from each"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer