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	7651
title	Fix: `IssueSyncer` fails to find releases after `ReleaseSyncer` refactoring
state	Closed
labels	bugai
assignees	tobiu
createdAt	Oct 25, 2025, 7:47 PM
updatedAt	Oct 25, 2025, 7:49 PM
githubUrl	https://github.com/neomjs/neo/issues/7651
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 25, 2025, 7:49 PM

Fix: `IssueSyncer` fails to find releases after `ReleaseSyncer` refactoring

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

Closed v11.0.0 bugai

tobiu commented on Oct 25, 2025, 7:47 PM

This ticket reports and resolves a bug introduced during the refactoring of ReleaseSyncer.mjs where ReleaseSyncer.releases was changed from an array to an object.

Problem: After ReleaseSyncer.releases was refactored from an array to an object, the IssueSyncer.#getIssuePath method, which relies on ReleaseSyncer.releases.find(), started failing with the error: ReleaseSyncer.releases.find is not a function. This prevented the sync_all tool from correctly processing and archiving closed issues.

Root Cause: The IssueSyncer.#getIssuePath method was attempting to use the find() array method directly on ReleaseSyncer.releases, which is no longer an array but an object.

Solution: The IssueSyncer.#getIssuePath method has been updated to correctly access the values of the ReleaseSyncer.releases object before attempting to use the find() method.

Changes Implemented: The following line in ai/mcp/server/github-workflow/services/sync/IssueSyncer.mjs was changed:

// Old:
const release = ReleaseSyncer.releases.find(r => new Date(r.publishedAt) > closed);

// New:
const release = Object.values(ReleaseSyncer.releases).find(r => new Date(r.publishedAt) > closed);

This ensures that the find() method is called on an array of release objects, resolving the error.

tobiu added the bug label on Oct 25, 2025, 7:47 PM

tobiu added the ai label on Oct 25, 2025, 7:47 PM

tobiu assigned to @tobiu on Oct 25, 2025, 7:47 PM

tobiu referenced in commit 5586f8a - "Fix: IssueSyncer fails to find releases after ReleaseSyncer refactoring #7651" on Oct 25, 2025, 7:48 PM

tobiu closed this issue on Oct 25, 2025, 7:49 PM