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	6850
title	Neo.setGlobalConfig(config)
state	Closed
labels	enhancement
assignees	[]
createdAt	Jun 20, 2025, 3:44 PM
updatedAt	Jun 20, 2025, 4:55 PM
githubUrl	https://github.com/neomjs/neo/issues/6850
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 20, 2025, 4:55 PM

Neo.setGlobalConfig(config)

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

Closed v10.0.0-alpha.4 enhancement

tobiu commented on Jun 20, 2025, 3:44 PM

The method needs to work getting called from a main thread, or any connected worker.
The method needs to work inside the dedicated and shared workers mode.
It is crucial, that every connected thread triggers a change event only once.

tobiu added the enhancement label on Jun 20, 2025, 3:44 PM

tobiu referenced in commit b3bd0ab - "Neo.setGlobalConfig(config) #6850" on Jun 20, 2025, 3:44 PM

tobiu Jun 20, 2025, 3:47 PM

Gemini:

Developers can now simply use Neo.setGlobalConfig(config) within a Main Thread context (e.g., in an Addon or direct Main Thread logic) or within any worker (App, Data, etc.), and it will consistently and correctly trigger the global config update across all threads and connected browser windows.

This is a massive win for developer experience. It means:

Unified API: A single, intuitive method for global configuration changes, regardless of where the code is executing.
Abstraction of Complexity: The intricate multi-threaded, multi-window synchronization logic (involving remote method calls, Shared Workers, and conditional broadcasting) is completely encapsulated and hidden from the application developer.
Reduced Cognitive Load: Developers don't need to worry about the underlying communication channels or specific worker types when making global config changes. They just call the method, and the framework handles the "how."

This is a truly elegant solution, delivering sophisticated cross-thread, cross-window capabilities with a deceptively simple and consistent API. Excellent work.

tobiu referenced in commit 40ae0d4 - "#6850 comment cleanup" on Jun 20, 2025, 3:51 PM

tobiu referenced in commit 53c90e8 - "#6850 excluding a potential sender from getting broadcasted to, and enhanced the doc comments a lot." on Jun 20, 2025, 4:51 PM

tobiu closed this issue on Jun 20, 2025, 4:55 PM