System overview

The System section explains the components that an administrator can inspect or configure through the HTTP UI. It is not an inventory of internal implementation details. It shows what each screen governs, which actions it permits, and what should be checked after a change.

The six areas

AreaWhat it governsTypical action
ModelsThe LLM contracts, embedding models, and vision model that are actually configured.Inspect a functional tier or change an editable configuration.
ServicesHealth, desired state, and placement of supervised components.Restart a known service and verify that it becomes healthy again.
LRE (Long Run Engine)Long-running, persistent tasks divided into accountable units.Follow a workload's progress, events, limits, and artifacts.
SafetyDeterministic signatures that allow, require approval for, or block commands.Understand why a particular action was admitted or stopped.
UsersIdentity, role, autonomy, paired channels, and preferences.Create a guest and grant only the autonomy they need.
DevicesPaired computers that can run remote executors.Pair, inspect, or revoke a device.

Inspect before acting

The administrative pages keep several easily confused facts separate. A process may be running but unhealthy; a service may be healthy while deliberately idle; a feature may be installed but disabled. Likewise, pairing a channel or device does not automatically grant every action. Identity, autonomy, policy, and executor authority remain separate controls.

A dependable change follows the same rhythm: read the effective state, choose an action from the closed catalog, wait for convergence, then re-read health and desired state. The UI does not expose a generic shell and does not turn arbitrary values into system commands.

Administrative access. These views may contain operational configuration and user data. Open them only through a trusted administrator session. The public documentation contains neither secrets nor personal values.

Finding your way around the HTTP UI

The real Metnos Services screen, showing System navigation and component cards in an Italian-language instance.
The Services page is a useful orientation point: it connects the System navigation tree to live operational state.
  1. System tree. Direct links to the six areas covered in this section.
  2. Overview. Summarises installed and running services and the refresh interval.
  3. Component card. Separates process state, application health, and desired state.
  4. Feature versus process. The LRE worker can be healthy while the feature remains deliberately disabled.
  5. Bounded actions. The UI displays only actions admitted for that service and state.

Captured from the real HTTP UI of an Italian-language instance. Identifying values, where present in this section, have been replaced with anonymous examples.