Why This Search Exists
Without a catalog, repeated browser tasks become inconsistent and harder to discover. Teams also lose clarity around where those tasks can run safely.
This makes the platform harder to scale across users and use cases.
Recommended Approach
An adapter catalog gives tasks stable names, arguments, and execution rules that can be shared consistently across CLI, MCP, and hosted surfaces.
iatlas-browser already provides the core model for this through its site surface and hosted subset.
Key Takeaways
- Catalogs scale better than informal browser scripts.
- Execution mode should be explicit in every command.
- Hosted-safe tasks belong on the remote layer.
- Session-aware tasks should stay local.
Fast Start
- Collect the repeated browser tasks your team uses most.
- Normalize command names and inputs.
- Separate hosted-safe and local-only execution modes.
- 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.