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	7732
title	bug: sync_all does not move existing local issues to archive on new release
state	Closed
labels	bugai
assignees	tobiu
createdAt	Nov 9, 2025, 11:31 AM
updatedAt	Nov 9, 2025, 2:49 PM
githubUrl	https://github.com/neomjs/neo/issues/7732
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 9, 2025, 2:49 PM

bug: sync_all does not move existing local issues to archive on new release

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

Closed v11.0.1 bugai

tobiu commented on Nov 9, 2025, 11:31 AM

Summary

The sync_all tool fails to move existing local issues from the .github/ISSUE/ directory to the appropriate release archive folder when a new release is synced.

Steps to Reproduce

Have a closed issue with a milestone (e.g., v11.0.0) that already exists as a local file in .github/ISSUE/.
Publish the corresponding release (v11.0.0) on GitHub.
Run the sync_all tool.

Expected Behavior

The local issue file is moved from .github/ISSUE/ to .github/ISSUE_ARCHIVE/11.0.0/. The local metadata in .github/.sync-metadata.json is updated with the new file path.

Actual Behavior

The local issue file is not moved. The sync logic appears to skip re-evaluating the location of local files if their content hash has not changed, even though its milestone now dictates it should be archived.

Technical Analysis

The bug is likely within the IssueSyncer service. The current logic prioritizes content hash checking over location validation. The logic needs to be refactored to ensure that for every issue pulled from GitHub, its correct local path (active vs. archived) is determined based on its milestone, and the local file is moved if its current path does not match the expected path. This location check must happen independently of the content sync check.

tobiu added the bug label on Nov 9, 2025, 11:32 AM

tobiu added the ai label on Nov 9, 2025, 11:32 AM

tobiu assigned to @tobiu on Nov 9, 2025, 11:40 AM

tobiu referenced in commit 931f151 - "bug: sync_all does not move existing local issues to archive on new release #7732" on Nov 9, 2025, 11:51 AM

tobiu referenced in commit 08198d3 - "#7732 safety net" on Nov 9, 2025, 11:59 AM

tobiu referenced in commit e135746 - "#7732 new test" on Nov 9, 2025, 12:28 PM

tobiu referenced in commit acd0c17 - "#7732 WIP" on Nov 9, 2025, 1:29 PM

tobiu referenced in commit 94bf401 - "#7732" on Nov 9, 2025, 2:40 PM

tobiu closed this issue on Nov 9, 2025, 2:49 PM