Why This Search Exists
When these interfaces are blurred together, teams struggle to understand where a task should run and what assumptions each path carries about state, trust, and environment.
That slows adoption and produces brittle operational behavior.
Recommended Approach
A structured browser ops model keeps one local runtime at the center for stateful work, exposes it through CLI and MCP, and then adds a separate hosted API layer for public tasks. This creates both power and clarity.
iatlas-browser is already organized around that structure.
Key Takeaways
- Clarity of interface matters as much as capability breadth.
- CLI, MCP, and hosted APIs solve different entry-point needs.
- One local runtime should anchor stateful work.
- Hosted APIs should stay narrow and remote-safe.
Fast Start
- Define the role of each interface in your workflow.
- Route stateful work through the local runtime.
- Expose the local runtime through MCP for agents.
- Use hosted APIs for public stateless operations.
Next Action
Read product overview
Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.