Why This Search Exists
Without an adapter catalog, teams rely on bookmarks, copied snippets, and individual habits. That makes browser work hard to share and hard to improve.
The problem grows when no one knows whether a given task is safe to run remotely or must stay local.
Recommended Approach
A catalog of adapters with explicit arguments and execution mode makes browser tasks easier to discover and easier to standardize.
iatlas-browser already follows this model with its `site` surface and hosted subset.
Key Takeaways
- Named adapters scale better than one-off scripts.
- Execution mode should be explicit in every catalog entry.
- Hosted subsets are best for public, read-only tasks.
- Session-aware tasks should remain local.
Fast Start
- Audit the browser tasks your analysts repeat each week.
- Define stable names and argument shapes for those tasks.
- Publish remote-safe tasks to the hosted subset when possible.
- Keep stateful tasks on the local runtime.
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.