Why This Search Exists
Without adapters, browser workflows stay fragmented and hard to improve. The same process gets executed differently by every operator.
Execution mode also becomes blurry when teams do not know which workflows are safe to host and which are tied to local session state.
Recommended Approach
Site adapters provide a stable interface for repeated browser work, with explicit names, arguments, and execution boundaries.
iatlas-browser already supports this model through its site catalog and hosted subset.
Key Takeaways
- Reusable adapters improve consistency across teams.
- Execution mode should be explicit in the adapter model.
- Hosted adapters should stay remote-safe and read-only.
- Session-aware adapters should remain local.
Fast Start
- List the repeated browser-led workflows used across teams.
- Normalize the names and arguments for those workflows.
- Separate hosted-safe tasks from local-only tasks.
- Publish and document the resulting catalog.
Next Action
Browse adapters
Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.