backend diagnosis

BrowserOps Status

Public-safe diagnosis for the browser evidence pipeline: persistence, Browserbase, trace storage, event recovery, integration handoffs, and Vercel AI Gateway readiness.

Status JSON

Run registry

persistent

Neon database is configured.

persistent

Browser runtime

browserbase

Browserbase configured

browserbase

Trace Postgres

missing_tables

Trace Postgres connection is configured, but required table(s) are missing: traces, spans, trace_evidence.

missing tables

Event storage

persistent

DATABASE_URL is configured; BrowserOps events are written to the outbox table and mirrored in process memory for live UI updates.

persistent

AI Gateway

degraded

AI Gateway is partially configured; BrowserOps can show diagnosis but should not depend on model calls yet.

degraded

Suite registry

12 lanes

Canonical BrowserOps integration registry with service-owned handoff paths.

12 lanes

degraded

Vercel AI Gateway Diagnosis

AI Gateway is partially configured; BrowserOps can show diagnosis but should not depend on model calls yet.

Diagnostic JSON Vercel docs

AI SDK

^7.0.59

gateway-compatible provider/model routing

Auth mode

oidc

Values are detected server-side and never exposed.

Default model

missing

Expected format: provider/model.

AI SDK gateway compatibility

passed

ai ^7.0.59 is installed and compatible with provider/model gateway routing.

Gateway authentication

passed

VERCEL_OIDC_TOKEN is present for local Vercel AI Gateway authentication.

Direct provider key bypass

passed

No direct provider API keys were detected in the BrowserOps environment.

Provider/model string

warning

No default AI Gateway model is configured. BrowserOps will require callers to provide an explicit provider/model id before making model calls.

Next diagnosis

Choose a supported provider/model id from the Vercel AI Gateway model catalog before enabling model-backed remediation.

honest degraded states

Current gaps and next actions

BrowserOps lists gaps instead of filling the dashboard with fake successful runs.

Open integration lanes

Trace Postgres connection is configured, but required table(s) are missing: traces, spans, trace_evidence.

AI Gateway is partially configured; BrowserOps can show diagnosis but should not depend on model calls yet.

Downstream handoffs remain preview or managed-dispatch until a confirmed service response exists.