Skip to content

Panel Overview

LexiSuite edited this page Nov 8, 2026 · 1 revision

Panel Overview

Use Overview to see what the node is actually running, how many model files and instances have been detected, and the next action to take. Open Overview at / (or use /rust or /rust/overview). These three entries render the same native overview, including on a fresh installation without configured instances. Setup and enrollment remain separate at /setup.

Read the landing screen

  1. Read Local models for the count of discovered model files. A discovered file is not proof it is loadable or verified.
  2. Read Instances for the configured instance count. Use Open Status to review and control an instance.
  3. Read Selected runtime. Running and reporting healthy requires a running instance and a healthy status from the current owner. Otherwise the page explicitly says Not confirmed healthy.
  4. Select the Next action link: Download a model, Create an instance, Inspect instance health, or Open Chat. Opening the link does not perform a mutation.
  5. Use First-run walkthrough, Guided tasks, Find a feature, or Help topics for assistance. The Status, Statistics, Logs, Diagnostics, and Notifications links open the respective existing pages.

The Overview values are server snapshots. The Status and Statistics pages also show small read-only live status/telemetry observations when scripting is enabled; their existing static content remains usable when it is not. A failed status read is shown as unavailable, not as a healthy node. Consult Panel Navigation and Help for the area index and feature search.

First-run walkthrough

On a new install, complete Set up administrator (new installs) on /setup before signing in; existing installations skip enrollment. Then:

  1. Get a model — open Download, submit a file URL, and wait for the model to appear in the Model library. A queued download does not mean the file is ready.
  2. Choose an engine — verify an installed runtime and a matching device/backend in Builds.
  3. Create an instance — choose a local model and enter Instance name, Engine, Device, Backend, Context, and Port as presented. Create instance does not start it.
  4. Start and check — select Start for an existing instance, then use Refresh health check until runtime status reports ready; acceptance alone is not readiness.
  5. Chat — open LexiChat and select the running model.

The administrator-only Serve your first model task (/rust/overview/tasks/overview.first-run) exposes the corresponding registered download, create, start, health, and undo operations as explicit steps, with confirmation before mutations. Enter the returned download id for cancellation; stop a running instance before deleting it. A step's accepted response does not substitute for inspecting later system state.

Overview and first-run controls

Control What it does (tooltip text) Page API routes Classic selector
Overview (overview.dashboard) Shows the current node, configured instances, and the safest next action without starting anything. /rust/overview GET /api/ux/overview —
Model library (overview.model-readiness) Lists discovered model files; a local file is not proof it can be loaded. /rust/overview GET /api/first-run #models
Instances (overview.instance-readiness) Shows configured instances and links to their start, stop, and settings controls. /rust/overview GET /api/instances #status
Runtime health (overview.health-readiness) Checks the selected instance's running state and health before offering Chat. /rust/overview GET /api/status —
Next action (overview.next-action) Opens the next setup step based on what the Panel has actually detected. /rust/overview GET /api/ux/overview —
First-run walkthrough (overview.first-run) Walk through model download, instance creation, starting, health verification, and Chat. /rust/help/walkthrough GET /api/first-run; POST /api/instance/create; POST /api/start —
Administrator setup (overview.account-setup) Creates the first administrator during one-time setup before the Panel accepts normal sign-ins. /rust/help/walkthrough — —
Download model (overview.download) Opens the download form; only completed model files can be selected for a new instance. /rust/help/walkthrough POST /api/download; GET /api/downloads #download
Create instance (overview.create) Creates an instance for a chosen local model, engine, device, and port; it does not start it. /rust/help/walkthrough POST /api/instance/create #status
Start instance (overview.start) Requests a start for the selected instance; check health before sending requests. /rust/help/walkthrough POST /api/start #status
Open Chat (overview.chat) Opens Chat after a running instance reports a healthy response. /rust/overview GET /api/status —
Refresh status (overview.status-refresh) Fetches a new runtime snapshot without restarting or reconfiguring any instance. /rust/status GET /api/status #status
Refresh statistics (overview.statistics-refresh) Reloads recorded request statistics and charts from a new server snapshot. /rust/statistics GET /api/stats —
Refresh logs (overview.logs-refresh) Reloads bounded logs; use the filters to narrow what is shown. /rust/logs GET /api/logs #logs
Refresh diagnostics (overview.diagnostics-refresh) Loads new diagnostic observations and the available debug-kit controls. /rust/diagnostics GET /api/diagnostics —

Read-only snapshot and action routes

GET /api/ux/overview summarizes GET /api/first-run into models_count, instances_count, healthy, instance, next_label, next_url, and snapshot. The underlying owner also obtains live instance state using GET /api/instances and GET /api/status. These endpoints never start an engine. Actions use the existing POST /api/download, POST /api/instance/create, POST /api/start, POST /api/stop, POST /api/instance/delete, and POST /api/download/cancel routes, with the normal permissions and validation rules.

See Panel Instances, Panel Models, Panel LexiChat, and Panel Diagnostics for the specific operational pages.

Shared page frame

Every Panel page has one header, one Primary navigation landmark, a Search features, settings and tasks field, the main-content skip target and a page guide. The page guide explains the registered capability, links to Help, and shows Open guided task when an appropriate task is available to the caller. Page controls and returned results stay with their native owner, rather than moving to a second interface. The theme and language controls remain available without scripting.

Navigation and Help describes the eight task-oriented groups and feature search.

Clone this wiki locally