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	6584
title	Polishing the ServiceWorker implementation
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Mar 25, 2025, 11:27 AM
updatedAt	Mar 25, 2025, 6:32 PM
githubUrl	https://github.com/neomjs/neo/issues/6584
author	tobiu
commentsCount	1
parentIssue	null
subIssues	6585 worker.ServiceBase: create a separate cache for each version 6586 worker.ServiceBase: onInstall() => remove the skipWaiting() call 6587 worker.Manager: add controllerchange SW listener as early as possible 6588 worker.ServiceBase: onFetch() => limit caching to event.request.method === ''GET'' 6589 main.addon.ServiceWorker: registerServiceWorker() 6590 main.addon.ServiceWorker: registerServiceWorker() => updatefound listener 6591 worker.ServiceBase: onActivate() => clear previous caches
subIssuesCompleted	7
subIssuesTotal	7
blockedBy	[]
blocking	[]
closedAt	Mar 25, 2025, 6:32 PM

Polishing the ServiceWorker implementation

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

Closed v8.33.0 enhancement

tobiu commented on Mar 25, 2025, 11:27 AM

While the current implementation works fine for caching related assets and even predictive caching via a MessageChannel connection to the app worker, it sometimes faces issues when deploying a new framework version to the online examples & website.

My assumption is, that the registerNeoConfig message arrives too late. Webpack can create different bundle file names, a previously cached asset is no longer available, which might result in a bug inside a main-thread and thus can prevent a reload.

Let's see if @dfabulich 's old guide can help a bit: https://redfin.engineering/how-to-fix-the-refresh-button-when-using-service-workers-a8e27af6df68

I will create sub-tasks (tickets).

tobiu added the enhancement label on Mar 25, 2025, 11:27 AM

tobiu assigned to @tobiu on Mar 25, 2025, 11:27 AM

tobiu added sub-issue #6585 on Mar 25, 2025, 11:29 AM

tobiu added sub-issue #6586 on Mar 25, 2025, 11:30 AM

tobiu added sub-issue #6587 on Mar 25, 2025, 11:33 AM

tobiu added sub-issue #6588 on Mar 25, 2025, 11:36 AM

tobiu added sub-issue #6589 on Mar 25, 2025, 2:06 PM

tobiu added sub-issue #6590 on Mar 25, 2025, 6:13 PM

tobiu added sub-issue #6591 on Mar 25, 2025, 6:17 PM

tobiu Mar 25, 2025, 6:32 PM

https://youtu.be/UG1JOeUSyEU

tobiu closed this issue on Mar 25, 2025, 6:32 PM