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	8710
title	Feature: Implement "Neural Lattice" Canvas for Services View
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 16, 2026, 4:47 PM
updatedAt	Jan 16, 2026, 4:49 PM
githubUrl	https://github.com/neomjs/neo/issues/8710
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 16, 2026, 4:49 PM

Feature: Implement "Neural Lattice" Canvas for Services View

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

Closed v11.23.0 enhancementai

tobiu commented on Jan 16, 2026, 4:47 PM

This task implements a new visual theme for the 'Services' view background, replacing the initial static network concept with a dynamic "Neural Lattice".

Concept: "The Neural Lattice" visualizes the Neo.mjs runtime as a high-frequency, structured logic floor (Motherboard/VDOM Registry).

Features:

Hexagonal Lattice: A tiling grid representing efficient structure and engineering.
High-Speed Runners: "Data Packets" or "Beams" that traverse the grid edges at high velocity, simulating multi-threaded throughput.
Topological Mutation (Runtime Permutation):
- Nodes accumulate "Build Charge" from runner traffic.
- High-traffic areas trigger a "Compilation" event, fusing 7-hex clusters into larger "Super Modules".
- These modules persist briefly before dissolving, visualizing dynamic component composition.
Inspection Lens: Mouse interaction creates a "Time Dilation" and focus effect, illuminating the underlying grid structure.

Implementation:

Zero-Allocation Architecture: Uses Float32Array buffers for Cells and Runners to maintain 60fps.
Canvas API: Custom hexagonal drawing and gradient trail rendering.
SharedWorker: Runs entirely off the main thread.

This addresses the feedback to better represent the "Application Engine" identity of the framework.

tobiu added the enhancement label on Jan 16, 2026, 4:47 PM

tobiu added the ai label on Jan 16, 2026, 4:47 PM

tobiu assigned to @tobiu on Jan 16, 2026, 4:48 PM

tobiu Jan 16, 2026, 4:49 PM

Input from Gemini 3 Pro:

✦ Implemented the "Neural Lattice" concept.

Key Changes:

Hexagonal Grid: Replaced the triangular mesh with a structured hex lattice.

Runners: Added high-velocity data beams (5-9 * scale speed) that traverse grid edges.

Dynamic Permutation: Implemented a charge-based system where runner congestion triggers the formation of "Super Hex" modules, which then dissolve back into the grid.

Visuals: Tuned colors and gradients for a "High-Tech / Engineering" aesthetic, distinct from the organic "Neural Swarm" of the Home view.

This implementation provides a more fitting visual metaphor for the "Application Engine" identity.

tobiu closed this issue on Jan 16, 2026, 4:49 PM