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	7025
title	Fix: EffectBatchManager.endBatch() Infinite Loop Prevention
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Jul 12, 2025, 7:54 PM
updatedAt	Jul 12, 2025, 7:56 PM
githubUrl	https://github.com/neomjs/neo/issues/7025
author	tobiu
commentsCount	0
parentIssue	6992
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jul 12, 2025, 7:56 PM

Fix: EffectBatchManager.endBatch() Infinite Loop Prevention

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

Closed v10.0.0-beta.6 enhancement

tobiu commented on Jul 12, 2025, 7:54 PM

Describe the bug The EffectBatchManager.endBatch() method, responsible for executing pending effects, had a subtle bug that could lead to an infinite loop. If an effect being run within the forEach loop caused another effect (or itself) to be re-queued into pendingEffects synchronously, it could result in the forEach iterating indefinitely or triggering subsequent endBatch() calls in a recursive manner.

To Reproduce Steps to reproduce the behavior:

Have an Neo.core.Effect (Effect A) that, when run, triggers a reactive change.
Have another Neo.core.Effect (Effect B) that depends on the reactive change caused by Effect A.
If Effect A is processed by EffectBatchManager.endBatch() and its execution synchronously causes Effect B to be re-queued into pendingEffects (or if Effect A itself is re-queued), it could lead to an infinite loop within the endBatch()'s forEach iteration.

Expected behavior The EffectBatchManager.endBatch() should process all pending effects in a given batch without re-triggering effects within the same batch, even if their execution causes new effects to be queued.

Solution To prevent this, EffectBatchManager.endBatch() now creates a snapshot of pendingEffects (using Array.from()) and clears the original pendingEffects Set before iterating and running the effects. This ensures that any new effects queued during the execution of the current batch are added to a new batch, preventing interference with the current processing and breaking the synchronous infinite loop.

Impact This bug could lead to application freezes and "Maximum call stack size exceeded" errors in scenarios where effects trigger other effects synchronously within a batch.

Affected Files src/core/EffectBatchManager.mjs

tobiu assigned to @tobiu on Jul 12, 2025, 7:54 PM

tobiu added the enhancement label on Jul 12, 2025, 7:54 PM

tobiu referenced in commit 98ff9b1 - "Fix: EffectBatchManager.endBatch() Infinite Loop Prevention #7025" on Jul 12, 2025, 7:56 PM

tobiu closed this issue on Jul 12, 2025, 7:56 PM

tobiu added parent issue #6992 on Jul 12, 2025, 8:27 PM