Trace

Timeline observability for agent, tool, API, BrowserOps, Evals, Sandbox, AgentUI, Claws, and CLI activity.

Browserbase lane

Validate Trace in BrowserOps

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

Preview JSON

Target: https://trace.platphormnews.com
Journey: Vercel alias snapshot 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 degraded

Live Public Connectivity

Trace public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.

Live JSON

health

200passed

trace echoed

apiDocs

200passed

trace echoed

llms

200passed

trace echoed

mcp

200passed

trace echoed

handoffReceiver

no responsedegraded

trace echo not confirmed

Browserbase Runtime

BrowserOps runs for Trace 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.

Capability Mapping

BrowserOps may call

open_trace
append_public_safe_span

BrowserOps may receive

trace_context_join_requested

Transport and Boundary

Preferred transports: openapi, trace, webhook
API docs: https://trace.platphormnews.com/api/docs
MCP status: not advertised
Auth boundary: Public-safe trace summaries may be linked; detailed writes and sensitive trace inspection use BrowserOps-managed service credentials or service-to-service authorization.

Handoff Examples

browseropstotraceplanned

Trace remains the observability spine; BrowserOps carries trace context and only claims export after confirmation.