MirrorNeuron Web UI

mn-web-ui is the React/Vite browser interface for operating persistent MirrorNeuron jobs and inspecting their execution runs, workflow graphs, events, artifacts, runtime resources, and models through mn-api.

The main lifecycle surfaces are intentionally separate:

• Jobs use /api/v1 and own reusable configuration, schedules, shared data, and run history.
• Runs are individual executions. Lifecycle controls, live progress, monitor snapshots, agent graphs, events, and artifacts use /api/v1.

The run monitor defaults to a selectable public-step list and can switch to the equivalent workflow graph. Both modes consume the same workflow-progress contract as mn job monitor; runtime-only control nodes are not UI steps.

Quick Start

Install dependencies and start the development server:

npm install
export MN_ENV=dev
cp .env.example .env.dev
npm run dev

Run local checks:

npm run lint
npm test -- --run
npm run build

Default local URL:

http://localhost:55173

Details

• MirrorNeuron Component Guide
• Monitor Guide
• API Reference

Notes

• Start mn-api before using live runtime screens.
• The configured API base may still point at /api/v1 for runtime-wide inventory endpoints; all job and execution monitoring derives and uses the sibling /api/v1 base.
• Set MN_WEB_API_TOKEN when connecting to a protected API instance.
• Blueprint-owned interfaces are external-url service handles. Service pages remain under the local /jobs/:jobId/ui route: the local Web UI server proxies only the job's declared dashboard, video, and WebSocket companion ports, so the browser never needs to navigate directly to a remote runtime node. Paused, stopped, cancelled, and failed services show a lifecycle message instead of framing a dead upstream.

Configuration

Configuration is defined in config/definitions.ts and loaded by config/node.ts. The loader uses this precedence:

real environment variables
> .env.${MN_ENV}
> .env
> built-in safe defaults

MN_ENV defaults to dev when unset. dev and development load .env.dev, test loads .env.test, and prod or production load .env.prod when it exists. Production does not require any .env file.

Development example:

export MN_ENV=dev
cp .env.example .env.dev
npm run dev

Test example:

export MN_ENV=test
npm test -- --run

Production example:

export MN_ENV=production
export MN_HOME=/var/lib/mirrorneuron
export MN_LOG_LEVEL=info
export MN_API_HOST=0.0.0.0
export MN_API_PORT=8080
export MN_WEB_API_BASE_URL=/api/v1
npm run build

Do not commit real .env files. Use .env.example for documented placeholders only, and provide secrets such as MN_WEB_API_TOKEN through deployment environment variables.

Blueprint catalog information comes from the canonical package manifest and its role documents. Validation errors identify the document and JSON Pointer to correct. See the blueprint format.