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	7381
title	Create a Robust GitHub CLI Setup and Verification Script
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfestai
assignees	LemonDrop847
createdAt	Oct 5, 2025, 5:57 PM
updatedAt	Oct 23, 2025, 12:51 AM
githubUrl	https://github.com/neomjs/neo/issues/7381
author	tobiu
commentsCount	3
parentIssue	7364
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 13, 2025, 11:15 PM

Create a Robust GitHub CLI Setup and Verification Script

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfestai

tobiu commented on Oct 5, 2025, 5:57 PM

To ensure all contributors have a consistent and functional environment for using our gh-based workflows, we need a setup script. This script will verify that the GitHub CLI is installed, authenticated, and up-to-date. This task is based on feedback from an external review which highlighted potential gaps in our contributor setup process.

Acceptance Criteria

A new build script is created (e.g., buildScripts/ai/verifyGhSetup.mjs).
The script must detect the user's OS (macOS, Linux, Windows).
It must check if gh is installed and provide OS-specific installation instructions if it is not (including for Windows).
It must run gh auth status to verify the user is logged in, and prompt them to run gh auth login if they are not.
It must check the gh --version against a minimum required version and instruct the user to upgrade if necessary.
The script should be added to package.json so it can be run easily (e.g., npm run ai:verify-gh-setup).

tobiu added the enhancement label on Oct 5, 2025, 5:57 PM

tobiu added the help wanted label on Oct 5, 2025, 5:57 PM

tobiu added the good first issue label on Oct 5, 2025, 5:57 PM

tobiu added the hacktoberfest label on Oct 5, 2025, 5:57 PM

tobiu added the ai label on Oct 5, 2025, 5:57 PM

tobiu added parent issue #7364 on Oct 5, 2025, 5:57 PM

LemonDrop847 Oct 5, 2025, 6:09 PM

would like to try this

tobiu assigned to @LemonDrop847 on Oct 5, 2025, 6:09 PM

tobiu Oct 5, 2025, 6:09 PM

thx! assigned.

LemonDrop847 cross-referenced by PR #7382 on Oct 5, 2025, 6:34 PM

tobiu Oct 13, 2025, 11:15 PM

closing the ticket as resolved.

tobiu closed this issue on Oct 13, 2025, 11:15 PM