← Agent catalogue
Operator console (Next.js)

Preview portrait

Interface

Operator console (Next.js)

Primary control-plane experience for pilots and demos; uses cookie-based JWT to `/api/v1/*` (see `apps/web/middleware.ts`).

LiveCatalogue status
Execution activeRuntime posture

Tenant-scoped operator UI: interactions list, command & execution views, overview metrics, connectors, approvals, interaction detail, and this Agent Overview map.

Open consoleBook a Demo

Expanded capabilities

  • Render the operator console with Standard Surface Contract honesty
  • Call live `/api/v1` command surfaces via apiRequest
  • Show skeleton/empty/unavailable states instead of fake fixtures
  • Cascade approvals, governance, and OS modules to phone form factors
  • Never mutate as a side effect of a read

How they learn & improve

Console UX improves from FEEDBACK and product design cycles — UI never silently approves, sends, or reconnects connectors.

  1. Load command DTOs with source-health metadata.
  2. Capture FEEDBACK on confusing assists.
  3. Ship UX calibrations through reviewed releases, not runtime self-edits.

Practical benefits

  • Empty means emptyNew tenants see why/what/what-now empty states instead of demo theatre.
  • Phone cascadeApprovals and governance remain usable at 375×812 with tactical chrome.
  • Reads don’t mutateOpening a dashboard never quietly refreshes OAuth or sends mail.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

Related agents

Operator console (Next.js) — AgentIQ Agent Catalogue · AgentIQ Labs