AgentUI

Visual workflow orchestration and tool UI rendering.

Browserbase lane

Validate AgentUI in BrowserOps

BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over AgentUI's product role.

Preview JSON

Target: https://agentui.platphormnews.com
Journey: Agentui homepage smoke

Boundary

Public preview validates intent. Browserbase runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.

Integration run state

Preview the BrowserOps plan publicly, then run a Browserbase-backed check through BrowserOps-managed service credentials.

live passed

Live Public Connectivity

AgentUI is reachable for public discovery. Use Browserbase-backed runs for browser evidence.

Live JSON

health

200passed

trace echo not confirmed

apiDocs

200passed

trace echo not confirmed

llms

200passed

trace echo not confirmed

mcp

200passed

trace echo not confirmed

handoffReceiver

200passed

trace echoed

Browserbase Runtime

BrowserOps runs for AgentUI use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.

tight integration contract

AgentUI Handoff Lane

AgentUI requests browser validation for rendered workflow UI; BrowserOps returns screenshots, accessibility status, labels, navigation state, and trace-linked run evidence.

Preview plan

Public-safe, no run stored.

Run with Browserbase

Creates browser evidence for trusted targets.

Track handoff

No delivery claim without downstream response.

Capability Mapping

BrowserOps may call

validate_rendered_tool_ui
read_workflow_step
open_originating_workflow

BrowserOps may receive

browser_validation_requested
workflow_step_update

Transport and Boundary

Preferred transports: mcp, openapi, sse, webhook
API docs: https://agentui.platphormnews.com/api/docs
MCP status: not advertised
Auth boundary: Public workflow reads remain public-safe; workflow run updates use BrowserOps-managed service credentials or service-to-service authorization.

Handoff Examples

agentuitobrowseropspreview ready

AgentUI remains the workflow UI surface; BrowserOps proves what the browser saw.