Skip to main content

Source: docs/manual/ui-pages.md

This page is generated by site/scripts/sync-manual-docs.mjs.

UI Page Guide

Cruvero's React control plane is defined in cmd/ui/frontend/src/App.tsx with sidebar grouping from buildSidebarGroups in the same file.

Source: cmd/ui/frontend/src/App.tsx, cmd/ui/frontend/src/pages/*

Sidebar groups:

  • Operations: dashboard, runs, events, approvals, questions, replay, traces.
  • Runtime: tools, prompts, Knowledge Bases, memory, cost, flows, recent run-template shortcuts.
  • Governance: audit, security, immune, quota, PII.
  • Tenant: tenant settings and user management.
  • Admin: health, models, agents, MCP servers, tool settings, global settings.

Access Model

Cruvero uses route guards (ProtectedRoute requiredRole) and backend API authorization.

Role matrix

CapabilityViewerEditorAdmin
Read dashboards, runs, events, memory, tools, governance pagesYesYesYes
Approvals and questions actionsNoYesYes
Flow builder routesNoYesYes
Agents/MCP/settings routesNoNoYes

Primary Pages

Operations

  • /, /operations, /runs, /runs/:id, /replay, /runs/:id/replay
  • /approvals, /questions, /control, /events, /traces

Runtime

  • /tools, /prompts, /knowledge-bases
  • /memory*, /cost*
  • /flows, /flows/builder*, /flows/builder-v2*
  • /inspect, /speculation, /diff-test

Governance

  • /audit, /security, /immune, /quota, /pii

Tenant/Admin

  • /tenant, /tenant/users, /health, /models, /settings/model-prefs
  • /agents, /mcp, /settings, /settings/tools

Key User Journeys

1) Start and validate a new run

  1. Open /runs.
  2. Click New Run.
  3. Choose single-agent or multi-agent mode.
  4. Optionally load/save a template and select Knowledge Bases.
  5. Run preflight validation and swarm preview before launch.

2) Manage Knowledge Base context

  1. Open /knowledge-bases.
  2. Create or select a KB.
  3. Upload documents and trigger embedding.
  4. Apply KB linkage to a prompt registry agent/version.

3) Create and monitor an agent

  1. Open /agents.
  2. Click New Agent.
  3. Set capabilities, planner, trust score, and optional MCP binding.
  4. Track status, MCP liveness, trust, and versions from the same surface.