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	8424
title	Fix SourceParser to resolve fully qualified superclass names
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 8, 2026, 2:25 PM
updatedAt	Jan 8, 2026, 2:27 PM
githubUrl	https://github.com/neomjs/neo/issues/8424
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 8, 2026, 2:27 PM

Fix SourceParser to resolve fully qualified superclass names

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

Closed v11.19.0 bugai

tobiu commented on Jan 8, 2026, 2:25 PM

The SourceParser currently extracts the local identifier for the parent class (e.g., extends Base), which results in broken links in the class hierarchy map.

Task: Refactor ai/mcp/server/knowledge-base/parser/SourceParser.mjs to:

Capture a map of imports (Local Name -> Import Path).
When a class extends X, look up X in the import map.
Resolve the import path relative to the current file path.
Convert the resolved file path into a fully qualified Neo class name (e.g., src/container/Base.mjs -> Neo.container.Base).

Heuristic:

Assume src/ maps to Neo..
Assume apps/ maps to App. (or use the app name from the path).
Handle relative paths (../, ./) using the path module (requires importing path).

Goal: The extends property in the chunk metadata should be a fully qualified class name (e.g., Neo.container.Base) whenever possible.

tobiu added the bug label on Jan 8, 2026, 2:25 PM

tobiu added the ai label on Jan 8, 2026, 2:25 PM

tobiu assigned to @tobiu on Jan 8, 2026, 2:26 PM

tobiu referenced in commit 3bda6e5 - "fix: Resolve fully qualified superclass name in SourceParser (#8424)" on Jan 8, 2026, 2:26 PM

tobiu Jan 8, 2026, 2:26 PM

Input from Gemini 3 Pro:

✦ I have updated SourceParser.mjs to resolve the fully qualified superClass name.

Logic Implemented:

Import Mapping: The parser now scans ImportDeclaration nodes and builds a map of localName -> importPath.

Resolution: When a class extends a local identifier (e.g., extends Container), the parser:

Looks up the import path for Container (e.g., ../../container/Base.mjs).

Resolves this relative to the current file path (src/tab/header/Toolbar.mjs + ../../container/Base.mjs -> src/container/Base.mjs).

Converts the resolved path into a Neo class namespace (Neo.container.Base) using standard conventions.

This ensures the extends metadata in the knowledge base (and thus the ai-class-hierarchy.json) points to valid, unique class keys rather than ambiguous local names.

tobiu closed this issue on Jan 8, 2026, 2:27 PM