Browser agents and MCP bridges

What Torsionfield extracts from multi-agent extensions, local-first browser tooling and Chromium agent platforms.

Nanobrowser

The Apache-2.0 project is a useful direct reference for a browser side panel, task history, multi-agent role separation and provider flexibility. Torsionfield should map these ideas onto durable agent identities, explicit operation routing and evidence rather than retaining a separate agent runtime.

AIPex

The AIPex/open-claude-for-chrome architecture demonstrates local-first browser tooling exposed through MCP and a compact representation of browser state. Relevant capabilities are tool registration, WebSocket/MCP transport and user-owned model/provider configuration.

BrowserOS

A Chromium fork can provide guarantees extension APIs cannot: native protected tabs, trusted input, browser-process tracing, integrated tools and CLI control. Because BrowserOS is AGPL-licensed, integration strategy must be consciously compatible or independently implemented.

Algonius

Algonius provides a strong reference for a typed Chrome extension plus native-messaging host that exposes browser capabilities over MCP. Torsionfield’s daemon bridge adds durable operation identity, capability policy and artifact journaling to this pattern.