Why This Search Exists
Without adapters, repeated browser tasks become scattered scripts and copied instructions with unclear boundaries around where they can run.
This weakens both discoverability and trust in the automation layer.
Recommended Approach
A site adapter model gives repeated tasks stable names, arguments, and execution mode that can be shared across interfaces.
iatlas-browser already follows this pattern through its site catalog and hosted subset.
Key Takeaways
- Reusable adapters scale better than scattered scripts.
- Execution mode should be explicit in every adapter.
- Hosted-safe tasks belong on the hosted layer.
- Session-aware tasks should remain local.
Fast Start
- List the repeated browser tasks used by your team.
- Normalize names and arguments for those tasks.
- Separate hosted-safe from local-only tasks.
- Publish the catalog across your browser surfaces.
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.