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	8760
title	Webpack: Exclude DefaultConfig from Bundles
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Jan 17, 2026, 6:01 PM
updatedAt	Jan 17, 2026, 6:57 PM
githubUrl	https://github.com/neomjs/neo/issues/8760
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 17, 2026, 6:57 PM

Webpack: Exclude DefaultConfig from Bundles

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

Closed v11.23.0 enhancementaibuild

tobiu commented on Jan 17, 2026, 6:01 PM

Description

For production builds (dist/production and dist/development), we rely on Webpack bundles. Currently, DefaultConfig.mjs might be bundled into the main chunk. To support the "Network First" strategy for version handshakes (Ticket #TBD), DefaultConfig.mjs must be excluded from the bundle so it can be requested independently and bypassed by the Service Worker's caching logic.

Tasks

Analyze current Webpack configuration for dist/production and dist/development builds.
Configure Webpack to exclude src/DefaultConfig.mjs from the main bundle.
Ensure DefaultConfig.mjs is copied/available as a standalone file in the output directory.
Verify that the application correctly loads the external DefaultConfig.mjs at runtime.

Acceptance Criteria

DefaultConfig.mjs is NOT part of the main Webpack bundle in dist builds.
The file exists as a separate asset in the build output.
The application boots correctly in dist/production mode.

tobiu added the enhancement label on Jan 17, 2026, 6:01 PM

tobiu added the ai label on Jan 17, 2026, 6:01 PM

tobiu added the build label on Jan 17, 2026, 6:01 PM

tobiu referenced in commit cd91bf0 - "feat: Exclude DefaultConfig from webpack bundles & Modernize ESM Output (#8760)" on Jan 17, 2026, 6:56 PM

tobiu Jan 17, 2026, 6:56 PM

Input from Gemini 3 Pro:

✦ I have completed the task to exclude DefaultConfig.mjs from the main bundle, enabling the Network-First strategy for version handshakes.

Key Changes:

Webpack Configuration (Dev & Prod):

Configured externals to exclude ./DefaultConfig.mjs.

Enabled experiments: { outputModule: true } and set output.library.type to 'module'. This ensures main.js is a native ES module that imports DefaultConfig.mjs correctly.

Updated output.publicPath to 'auto' to fix chunk loading in nested apps (native ESM resolution).

Added build hooks to copy (and minify for prod) DefaultConfig.mjs to the output folder using the new helper scripts.

Codebase Modernization:

Removed the legacy __webpack_require__.p path patching from src/main/DeltaUpdates.mjs. This hack is no longer needed with native ESM output and was causing conflicts.

Verification:

User verified that the Portal App loads correctly in dist/development mode.

Confirmed that main.js contains a native import statement for DefaultConfig.mjs.

Confirmed that chunks load correctly regardless of index.html location.

This architectural change robustly solves the version handshake issue and modernizes the build output.

tobiu assigned to @tobiu on Jan 17, 2026, 6:56 PM

tobiu closed this issue on Jan 17, 2026, 6:57 PM

tobiu cross-referenced by #8762 on Jan 17, 2026, 7:01 PM