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	7687
title	Enhance GitHub Workflow server robustness when gh cli is not installed
state	Closed
labels	enhancementai
assignees	MannXo
createdAt	Nov 1, 2025, 7:22 PM
updatedAt	Nov 10, 2025, 9:31 PM
githubUrl	https://github.com/neomjs/neo/issues/7687
author	tobiu
commentsCount	3
parentIssue	null
subIssues	7714 ci(testing): gate GitHub-integration tests and add diagnostics polish 7713 health(github-workflow): reproduce gh-absent
subIssuesCompleted	2
subIssuesTotal	2
blockedBy	[]
blocking	[]
closedAt	Nov 10, 2025, 9:31 PM

Enhance GitHub Workflow server robustness when gh cli is not installed

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

Closed v11.1.0 enhancementai

tobiu commented on Nov 1, 2025, 7:22 PM

The HealthService in the github-workflow MCP server currently checks for gh cli authentication and version. While robust, the server's behavior and error handling when gh cli is entirely absent or not in the PATH needs further investigation. This ticket is to thoroughly inspect and enhance the server's startup robustness and error messaging in such scenarios.

tobiu added the enhancement label on Nov 1, 2025, 7:22 PM

tobiu added the ai label on Nov 1, 2025, 7:22 PM

MannXo Nov 1, 2025, 7:39 PM

Hi, As you mentioned, I have already partially addressed this in #7678 . I'm happy to work on this ticket as well, if you see fit.

tobiu assigned to @MannXo on Nov 1, 2025, 7:45 PM

tobiu Nov 1, 2025, 7:49 PM

this one definitely makes sense: uninstalling gh cli completely and see if the server handles it.

bigger picture: to get v11 ready, i would like to fully remove siesta. to do this, we need to explore which unit tests and component based tests did not get migrated yet, and tackle them. we also need to update some guides and the agents file itself (i am currently having sessions where gemini fails to use the memory core without several recovery prompts). you are definitely welcome to open new tickets for any topics of interest.

i am already moving new mcp testing files into the playwright folder.

MannXo cross-referenced by #7713 on Nov 7, 2025, 9:28 AM

MannXo cross-referenced by #7714 on Nov 7, 2025, 9:30 AM

tobiu added sub-issue #7714 on Nov 7, 2025, 9:38 AM

tobiu added sub-issue #7713 on Nov 7, 2025, 9:48 AM

tobiu Nov 10, 2025, 9:31 PM

closing the epic, since all subs are resolved.

tobiu closed this issue on Nov 10, 2025, 9:31 PM