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	9444
title	Clean up redundant `Neo.isDestroyed` catch blocks
state	Closed
labels	enhancementairefactoringcore
assignees	tobiu
createdAt	Mar 11, 2026, 5:42 PM
updatedAt	Mar 15, 2026, 12:39 PM
githubUrl	https://github.com/neomjs/neo/issues/9444
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 11, 2026, 5:53 PM

Clean up redundant `Neo.isDestroyed` catch blocks

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

Closed v12.1.0 enhancementairefactoringcore

tobiu commented on Mar 11, 2026, 5:42 PM

The framework globally handles unhandled promise rejections for the Neo.isDestroyed symbol (inside src/Neo.mjs).

Because of this built-in global interceptor, individual .catch() blocks on promises (like those returned by this.trap()) that merely check for err !== Neo.isDestroyed and re-throw are redundant and add unnecessary boilerplate to the codebase.

We should clean up the remaining occurrences of this pattern in the src/ directory to simplify the code.

Occurrences found in:

src/worker/mixin/RemoteMethodAccess.mjs
src/component/Circle.mjs
src/component/Helix.mjs
src/component/MagicMoveText.mjs
src/mixin/DomEvents.mjs
src/core/Base.mjs

tobiu added the enhancement label on Mar 11, 2026, 5:42 PM

tobiu added the ai label on Mar 11, 2026, 5:42 PM

tobiu added the refactoring label on Mar 11, 2026, 5:42 PM

tobiu added the core label on Mar 11, 2026, 5:42 PM

tobiu referenced in commit f79713a - "refactor(core): Remove redundant catch blocks for globally handled Neo.isDestroyed exceptions (#9444)" on Mar 11, 2026, 5:52 PM

tobiu Mar 11, 2026, 5:52 PM

Input from Gemini 3.1 Pro:

✦ The redundant catch blocks checking for Neo.isDestroyed have been removed from the identified locations:

src/worker/mixin/RemoteMethodAccess.mjs

src/component/Circle.mjs

src/component/Helix.mjs

src/mixin/DomEvents.mjs

src/core/Base.mjs

(Note: The explicit check in src/component/MagicMoveText.mjs was intentionally left in place because it is not a redundant re-throw; it serves as a critical early exit (return;) before executing a visual retry fallback loop, which we do not want to trigger on a destroyed component).

The codebase is now cleaner, relying on the central unhandledrejection interceptors in src/Neo.mjs to silently swallow Neo.isDestroyed exceptions as designed.

tobiu closed this issue on Mar 11, 2026, 5:53 PM

tobiu assigned to @tobiu on Mar 15, 2026, 12:39 PM

Clean up redundant Neo.isDestroyed catch blocks

Clean up redundant `Neo.isDestroyed` catch blocks