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	8581
title	Fix outdated ticket index in release workflow
state	Closed
labels	bugai
assignees	tobiu
createdAt	Jan 12, 2026, 11:13 AM
updatedAt	Jan 12, 2026, 11:20 AM
githubUrl	https://github.com/neomjs/neo/issues/8581
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 12, 2026, 11:20 AM

Fix outdated ticket index in release workflow

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

Closed v11.21.0 bugai

tobiu commented on Jan 12, 2026, 11:13 AM

Problem

In the release workflow (publishRelease.mjs), createTicketIndex.mjs is executed during the "Prepare" phase (Step 2). However, the GH_SyncService.runFullSync() which moves closed tickets to the issue-archive folder runs in the "Post-Release Cleanup" phase (Step 6).

This results in tickets.json pointing to the old locations of tickets (in issues/) instead of their new archived locations (in issue-archive/vX.Y.Z/), causing broken links in the Portal application.

Solution

Regenerate the ticket index (createTicketIndex.mjs) in publishRelease.mjs immediately after the GH_SyncService completes its sync, ensuring tickets.json reflects the final file structure before the archive commit is created.

tobiu added the bug label on Jan 12, 2026, 11:13 AM

tobiu added the ai label on Jan 12, 2026, 11:13 AM

tobiu referenced in commit 869691c - "fix: Regenerate ticket index after archiving in release workflow (#8581)" on Jan 12, 2026, 11:20 AM

tobiu assigned to @tobiu on Jan 12, 2026, 11:20 AM

tobiu Jan 12, 2026, 11:20 AM

Input from Gemini 3 Pro:

✦ I have implemented the fix by ensuring createTicketIndex.mjs is run a second time in the release workflow, immediately after the GitHub sync service moves tickets to the archive. This ensures tickets.json correctly points to the new archived locations on the dev branch post-release.

I also manually regenerated the tickets.json index and included it in the commit to ensure the current state is correct.

tobiu closed this issue on Jan 12, 2026, 11:20 AM