Why This Search Exists
Without a reusable catalog, browser tasks multiply as one-off scripts and undocumented habits, which weakens both discoverability and execution clarity.
Teams especially need explicit boundaries around which commands are safe to host and which depend on local session state.
Recommended Approach
An adapter catalog gives tasks stable names, arguments, outputs, and execution rules so they can scale across CLI, MCP, and hosted surfaces.
iatlas-browser already has the structural pieces for this through its site model and hosted subset.
Key Takeaways
- Catalogs scale better than scattered browser scripts.
- Execution boundaries should be explicit in the adapter model.
- Hosted-safe adapters belong on the remote layer.
- Session-aware adapters should stay local.
Fast Start
- List the browser tasks your platform already exposes.
- Normalize their names, inputs, and outputs.
- Label hosted-safe and local-only execution clearly.
- Publish the resulting catalog consistently.
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.