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	7713
title	health(github-workflow): reproduce gh-absent
state	Closed
labels	[]
assignees	MannXo
createdAt	Nov 7, 2025, 9:28 AM
updatedAt	Nov 8, 2025, 11:05 AM
githubUrl	https://github.com/neomjs/neo/issues/7713
author	MannXo
commentsCount	1
parentIssue	7687
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 8, 2025, 11:05 AM

health(github-workflow): reproduce gh-absent

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

Closed v11.0.0 []

MannXo commented on Nov 7, 2025, 9:28 AM

Summary

Reproduce startup behavior when the GitHub CLI (gh) is entirely absent or not on the PATH; add unit tests for HealthService, implement an explicit ENOENT detection and a small non-blocking retry/backoff so the server recovers when gh becomes available, and add a short runbook/docs snippet with reproduction and remediation steps. (see parent issue #7687)

To do

Add reproducible instructions and a short script to simulate gh being absent (e.g., PATH modification) under ai/mcp/server/github-workflow/docs/gh-absent.md.
Add unit tests for HealthService that mock child_process.exec / execAsync to simulate these states:
- ENOENT (gh not installed / not in PATH)
- stdout empty + stderr-only output
- gh present but unauthenticated
- gh present but old version
Implement code changes in ai/mcp/server/github-workflow/services/HealthService.mjs to:
- Detect ENOENT explicitly and log a clear, actionable message ("gh CLI not found in PATH; tools will be disabled until installed")
- Return a consistent health status (degraded/unhealthy) without crashing the server
- Add a small non-blocking retry/backoff (configurable) for auth/version checks so the server can recover without restart
Add a short runbook/docs entry with reproduction steps and remediation commands.

Acceptance criteria

Reproduction steps and logs included in the issue or added doc file
Unit tests added covering the four states; tests pass locally and in CI
HealthService code updated with ENOENT handling and retry/backoff and no server crash on startup
PR references this issue and parent #7687

tobiu added parent issue #7687 on Nov 7, 2025, 9:48 AM

tobiu assigned to @MannXo on Nov 7, 2025, 9:49 AM

tobiu Nov 7, 2025, 9:52 AM

@MannXo Thanks for the new tickets. I assigned both to you, assuming that you want to tackle them. We are getting super close to v11 => all tests got migrated to playwright, and I fixed the combobox issues and created a faster and non-vulnerable version of jsdoc-x within the repo.

On my end, I will create the .npmignore next, and then polish the AI guides more.

MannXo cross-referenced by PR #7717 on Nov 7, 2025, 10:35 AM

tobiu closed this issue on Nov 8, 2025, 11:05 AM