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	7632
title	feat(mcp): Add tool to manage GitHub issue relationships
state	Closed
labels	enhancementai
assignees	MannXo
createdAt	Oct 24, 2025, 12:15 PM
updatedAt	Nov 12, 2025, 9:20 AM
githubUrl	https://github.com/neomjs/neo/issues/7632
author	tobiu
commentsCount	3
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 12, 2025, 9:20 AM

feat(mcp): Add tool to manage GitHub issue relationships

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

Closed v11.1.0 enhancementai

tobiu commented on Oct 24, 2025, 12:15 PM

This ticket is for creating a new tool within the GitHub Workflow MCP server to manage relationships between issues. Currently, parent/sub-issue relationships are managed manually by editing the markdown files. A dedicated tool would streamline this process.

Acceptance Criteria:

A new tool (e.g., update_issue_relationship) is added to the GitHub Workflow MCP server.
The tool should allow setting or unsetting the parentIssue field for a given issue.
The tool should automatically update the subIssues array on the parent issue when a child is added or removed.
The changes should be synced back to the local markdown files via the existing sync_all mechanism or a more direct update.

tobiu added the enhancement label on Oct 24, 2025, 12:15 PM

tobiu added the ai label on Oct 24, 2025, 12:15 PM

MannXo Nov 11, 2025, 10:13 AM

@tobiu I can take on this one if it's alright.

tobiu Nov 11, 2025, 10:28 AM

@MannXo this ticket is definitely a fascinating one. I have not looked into the API yet. Assuming that relationships do not contain comments, i would add this info at the bottom of each ticket (below comments). E.g. ## History or ## Relationships.

To get the idea: https://raw.githubusercontent.com/neomjs/neo/refs/heads/dev/.github/ISSUE/issue-7733.md

tobiu assigned to @MannXo on Nov 11, 2025, 10:28 AM

MannXo cross-referenced by PR #7741 on Nov 11, 2025, 11:39 AM

tobiu Nov 12, 2025, 8:47 AM

ha, i confused issue relationship and issue history :) i think we got another ticket for the ticket-timeline too somewhere. looking into the PR now.

tobiu closed this issue on Nov 12, 2025, 9:20 AM