Operations overview
Ta treść nie jest jeszcze dostępna w Twoim języku.
Operations overview
Section titled “Operations overview”LM Nexus tries to keep the machinery visible.
If a local model server starts, fails, consumes resources, or writes logs, you should be able to see enough of that state to understand what is happening instead of dealing with one opaque background process.
Runtime and process visibility
Section titled “Runtime and process visibility”Operational surfaces include:
- model and runtime status;
- logs;
- process state;
- health information;
- terminal access;
- selected infrastructure integrations.
LM Nexus should only clean up child processes it started. It should not terminate unrelated user-managed processes.
Logs and diagnostics
Section titled “Logs and diagnostics”Logs and diagnostics help narrow a problem down to categories such as:
- configuration;
- provider or network access;
- runtime startup;
- model or resource limits;
- application/module failures.
The public diagnostics guide will become more detailed as the release tooling settles.
Platform support today
Section titled “Platform support today”Current development and validation are centered on native Windows PowerShell.
The current native-Windows full-stack evidence covers the root launcher, backend and frontend, registered module flows, the ConPTY/pywinpty Terminal path, Agent Runtime, Model Manager, durable run state, and Nexus-owned process cleanup on a real Windows host.
Linux and Windows through WSL remain portability/compatibility paths in the repository, but they have not had the same recent maintainer validation. Do not infer current Linux or WSL parity from native-Windows evidence.
macOS is not currently part of the validated support target.
Troubleshooting
Section titled “Troubleshooting”See Troubleshooting for common startup, runtime, model, and provider problems.