Monitor gateway readiness, runtime selection, connection inventory, and memory visibility from one operator-facing status view. Last checked: 1:51:44 PM.
Status checks are waiting on the configured operator gateway.
Runtime selection is unavailable until the operator gateway grants browser access.
These counts are drawn from live channel and workstation registries stored by the gateway.
Operators can move directly from a health signal into the route that owns setup, inspection, or execution without relying on design-time placeholders.
Use these routes to inspect runtime state, move into execution, or reconfigure the operator path when a dependency is degraded.
Move into the portal for component, connection, and memory posture pulled from the live gateway.
Use chat when the next step is to execute, investigate, or route work through agents.
Use setup when the issue is configuration, credentials, or provider routing rather than service inspection.
These cards summarize live configuration data instead of shipping a static changelog into the status route.
Configured operator gateway currently used by the browser shell for portal, status, dashboard, and chat wiring.
Providers currently reporting configured credentials or host data through the runtime inventory.
Indexed memory records visible to the current browser session when memory access is permitted.
Portal is for telemetry, chat is for action, and setup is for correcting the gateway, runtime, or operator configuration behind the issue.