OpenBot puts browser, file, and MCP actions behind a policy gateway

CopilotKit’s alpha OpenBot project runs each bot with its own browser profile and workspace. Its gateway resolves a tool target, evaluates it against policy, writes an audit record, and then allows or refuses the action. Why it matters: An agent with browser or file access needs an enforcement point before it acts. OpenBot makes that boundary explicit, but the project is early and its local quick start starts as a single administrator unless sign-in is configured.

Try this: Read the architecture and policy sections, then compare one existing agent workflow against its sequence: resolve target, evaluate policy, record outcome, act or refuse.