What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9833
title	Refactor InferenceLifecycleService: Abstract spawn logic and integrate headless LM Studio auto-boot
state	Closed
labels	enhancementairefactoring
assignees	tobiu
createdAt	Apr 9, 2026, 9:16 PM
updatedAt	Apr 9, 2026, 9:17 PM
githubUrl	https://github.com/neomjs/neo/issues/9833
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 9, 2026, 9:17 PM

Refactor InferenceLifecycleService: Abstract spawn logic and integrate headless LM Studio auto-boot

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedenhancementairefactoring

tobiu commented on Apr 9, 2026, 9:16 PM

Architectural Context

The InferenceLifecycleService previously suffered from significant Promise/spawn boilerplate duplication across multiple local inference providers (Ollama, MLX). Furthermore, it failed to support autonomous headless initialization for LM Studio (1234), forcing manual GUI interaction upon agent OS reboots.

Implementation

Abstracted Spawn Logic: Consolidated the repetitive child_process.spawn and event-listener blocks into a unified spawnInferenceProcess(cmd, args, name) utility method.
Integrated LM Studio Auto-Boot: Added native auto-boot support for port 1234 utilizing the LM Studio CLI (lms server start).
Preserved Ollama / MLX: Restored and retrofitted Ollama and MLX to utilize the new abstract method, ensuring backward compatibility for the broader user base.
Collision Defense Verification: Validated that the existing isInferenceRunning() HTTP check correctly prevents zombie process duplication across all underlying engines by gracefully short-circuiting the spawn cycle if the port is already active.

Avoided Pitfalls

TCP Socket Contention: Duplication fears were mitigated by leveraging the native OS-level socket closures embedded within lms, ollama, and the mlx Python daemon.
Port Masking: Prevented accidental port collisions by strictly gating the LM Studio spawn behind the explicit 1234 check, separating it from Ollama's 11434 namespace.

tobiu added the enhancement label on Apr 9, 2026, 9:16 PM

tobiu added the ai label on Apr 9, 2026, 9:16 PM

tobiu added the refactoring label on Apr 9, 2026, 9:16 PM

tobiu referenced in commit 0a3812c - "feat: Refactor InferenceLifecycleService spawn logic (#9833)" on Apr 9, 2026, 9:16 PM

tobiu assigned to @tobiu on Apr 9, 2026, 9:16 PM

tobiu Apr 9, 2026, 9:17 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ Completed via commit 0a3812c4c.

The InferenceLifecycleService has been successfully refactored. The unified spawnInferenceProcess() method is implemented and autonomous headless support for the LM Studio CLI (port 1234) is active alongside retrofitted Ollama/MLX paths.

Verified the isInferenceRunning() HTTP check natively handles duplicated port contention across all engine providers.

tobiu closed this issue on Apr 9, 2026, 9:17 PM