infAct Browser

The browser automation shared tool is documented as infAct Browser in the product docs. The current runtime id is still browser-use.

That is an implementation choice, not the identity of infrastrActure itself.

Purpose

infrastrActure exposes browser automation as a shared tool because some agents need a real browser, a visible session, and a transport that can be observed from the frontend.

Runtime Shape

Why It Is Different

Most shared tools are only MCP runtimes.

The browser automation runtime also needs:

• a visible browser
• a display server
• a viewer transport
• more Docker runtime tuning than usual

Tier

In the current implementation, infAct Browser is a standard shared tool, with runtime id browser-use.

If the implementation changes later, this page should still describe the browser automation role rather than locking the docs to a single package name.