Why This Search Exists
Without a catalog, browser tasks are repeated through bookmarks, personal scripts, and informal habits that do not scale across teams.
Teams also lose clarity about which commands are safe to host and which depend on local session state.
Recommended Approach
A site adapter catalog gives teams reusable command names, argument contracts, and explicit execution mode.
iatlas-browser already supports this through its site surface and hosted subset.
Key Takeaways
- A catalog scales better than informal browser habits.
- Execution mode should be explicit in every adapter.
- Hosted adapters are for public remote-safe tasks.
- Session-aware adapters should stay local.
Fast Start
- Collect the browser tasks your team repeats most often.
- Normalize the names and argument shapes.
- Separate hosted-safe commands from local-only ones.
- Publish the catalog through your CLI, MCP, and hosted 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.