Adapter Catalog for Browser Research Workflows

Why This Search Exists

Without a catalog, research workflows are hard to share and hard to refine. The same browser tasks get rebuilt by different people in slightly different ways.

The team also loses clarity about which tasks belong on the hosted layer and which must stay local.

Recommended Approach

An adapter catalog with explicit execution mode gives research teams a more scalable operating model for browser tasks.

iatlas-browser already supports this pattern through its site surface and hosted subset.

Key Takeaways

• Reusable browser commands improve research consistency.
• Execution mode should be part of the adapter definition.
• Hosted tasks should stay public and read-only.
• Session-aware tasks should remain on the local runtime.

Fast Start

1. List the browser tasks your research team repeats regularly.
2. Define stable adapter names and arguments.
3. Separate hosted-safe tasks from local-only tasks.
4. Publish the catalog through the right surfaces.