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	7947
title	Fix: Sync missing sub-issues and enhance activity log
state	Closed
labels	bugenhancementai
assignees	tobiu
createdAt	Nov 30, 2025, 1:21 PM
updatedAt	Nov 30, 2025, 1:24 PM
githubUrl	https://github.com/neomjs/neo/issues/7947
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 30, 2025, 1:24 PM

Fix: Sync missing sub-issues and enhance activity log

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

Closed v11.14.0 bugenhancementai

tobiu commented on Nov 30, 2025, 1:21 PM

Problem

Local markdown files for issues (e.g., Epics) were not showing their sub-issues. This was because adding a sub-issue on GitHub does not update the parent issue's updatedAt timestamp, causing the delta-sync to skip the parent.

Solution

Implemented a "Child-Triggered Parent Refresh" strategy in IssueSyncer.mjs.

When fetching issues, we check if they have a parent.
We collect these parent IDs and force-update them in a post-processing step.
This ensures parents are updated whenever their children are active (created/updated).

Enhancements

Updated issueQueries.mjs to fetch ALL relationship events (SubIssueAdded, BlockedByAdded, etc.).
Updated IssueSyncer.mjs to format these events in the "Activity Log" section of the markdown.
Added intent-driven documentation explaining the sync strategy.

Files Changed

ai/mcp/server/github-workflow/services/sync/IssueSyncer.mjs
ai/mcp/server/github-workflow/services/queries/issueQueries.mjs

tobiu added the bug label on Nov 30, 2025, 1:21 PM

tobiu added the enhancement label on Nov 30, 2025, 1:21 PM

tobiu added the ai label on Nov 30, 2025, 1:21 PM

tobiu assigned to @tobiu on Nov 30, 2025, 1:22 PM

tobiu referenced in commit 5028ac9 - "Fix: Sync missing sub-issues and enhance activity log #7947" on Nov 30, 2025, 1:23 PM

tobiu Nov 30, 2025, 1:24 PM

Input from Gemini 3 (Experimental):

✦ Verification Successful

We have verified the fix with a live test case:

Created a new sub-issue #7946 and linked it to Epic #7931.

Confirmed that #7931's updatedAt timestamp on GitHub did not change.

Ran sync_all.

Observed that #7931 was correctly identified and updated in the local sync (along with #7946), proving the "Child-Triggered Parent Refresh" logic works as intended.

The sub-issue list for #7931 is now correctly populated in the local markdown file.

tobiu closed this issue on Nov 30, 2025, 1:24 PM