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	8063
title	Refactor LivePreview to use Pluggable Renderers
state	Closed
labels	enhancementairefactoringarchitecture
assignees	tobiu
createdAt	Dec 9, 2025, 1:25 AM
updatedAt	Dec 9, 2025, 2:26 AM
githubUrl	https://github.com/neomjs/neo/issues/8063
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 9, 2025, 2:26 AM

Refactor LivePreview to use Pluggable Renderers

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

Closed v11.17.0 enhancementairefactoringarchitecture

tobiu commented on Dec 9, 2025, 1:25 AM

Extract code rendering logic from Neo.code.LivePreview and markdown logic from Portal.view.learn.ContentComponent into dedicated renderer classes.

Goal: Enable Neo.code.LivePreview to support multiple languages (Neo.mjs code execution, Markdown rendering) via a pluggable renderer system.

Changes:

Create src/code/renderer/Base.mjs: Abstract base class for renderers.
Create src/code/renderer/Neo.mjs: Encapsulates logic for doRunSource, findClassNames, etc.
Create src/code/renderer/Markdown.mjs: Encapsulates logic for marked parsing, HighlightJS processing, and custom block extraction.
Refactor Neo.code.LivePreview:
- Add language config (enum: 'neomjs', 'markdown').
- Add renderer reactive config (instance of renderer).
- Update afterSetLanguage to dynamically import and instantiate the correct renderer.
- Delegate execution/rendering to the active renderer.
Refactor Portal.view.learn.ContentComponent:
- Use src/code/renderer/Markdown.mjs to parse content, removing duplication.

tobiu added the enhancement label on Dec 9, 2025, 1:25 AM

tobiu added the ai label on Dec 9, 2025, 1:25 AM

tobiu added the refactoring label on Dec 9, 2025, 1:25 AM

tobiu added the architecture label on Dec 9, 2025, 1:25 AM

tobiu assigned to @tobiu on Dec 9, 2025, 1:49 AM

tobiu referenced in commit c3b9bc0 - "Refactor LivePreview to use Pluggable Renderers #8063" on Dec 9, 2025, 1:50 AM

tobiu Dec 9, 2025, 1:53 AM

Input from Gemini:

✦ Refactoring complete.

Changes:

Pluggable Renderer Architecture:

Created src/code/renderer/Base.mjs (Abstract Base).

Created src/code/renderer/Neo.mjs (Neo.mjs code execution).

Created src/code/renderer/Markdown.mjs (Markdown parsing/rendering).

Neo.code.LivePreview Update:

Now uses language_ ('neomjs' | 'markdown') and renderer_ configs.

Dynamic import of renderers.

Delegates execution to the active renderer.

Portal.view.learn.ContentComponent Update:

Refactored to use Neo.code.renderer.Markdown, eliminating code duplication.

Path Resolution Fix:

Adjusted relative path resolution in Neo.mjs renderer for development environment to account for the new file location.

Verified by user in devmode (standalone and learning section).

tobiu closed this issue on Dec 9, 2025, 2:26 AM