Why This Search Exists
Without an adapter strategy, workflows sprawl into one-off scripts with unclear boundaries around which ones are safe to host and which require local browser state.
That makes the platform harder to document, discover, and evolve.
Recommended Approach
An adapter strategy gives tasks stable names, arguments, and explicit execution mode that can be shared across CLI, MCP, and hosted surfaces.
iatlas-browser already supports this structure through its `site` surface and hosted subset.
Key Takeaways
- Adapters scale better than one-off scripts.
- Execution mode should always be explicit.
- Hosted-safe tasks belong on the remote layer.
- Session-aware tasks should stay local.
Fast Start
- List the browser workflows shared across teams.
- Normalize their names and arguments.
- Separate hosted-safe from local-only tasks.
- Publish the resulting adapter strategy clearly.
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.