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	7306
title	Exploration Quest: Make the AI Aware of `buildScripts`
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfest
assignees	Saksham-chourasia
createdAt	Sep 28, 2025, 4:13 PM
updatedAt	Oct 24, 2025, 11:54 AM
githubUrl	https://github.com/neomjs/neo/issues/7306
author	tobiu
commentsCount	3
parentIssue	7296
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 24, 2025, 11:54 AM

Exploration Quest: Make the AI Aware of `buildScripts`

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfest

tobiu commented on Sep 28, 2025, 4:13 PM

This is a special "Exploration Quest" ticket. Your mission is to investigate and define the best way to make our AI agent aware of the valuable utility scripts located in the /buildScripts directory.

Currently, the AI has a blind spot: it does not know these tools exist, what they do, or how to use them. Your task is to solve this discovery problem.

The Quest

Investigate at least two potential solutions:

Full Knowledge Base Integration: This would involve modifying buildScripts/ai/createKnowledgeBase.mjs to parse all .mjs files within /buildScripts and add them to the vector database. This would give the AI deep, semantic knowledge of the scripts' content.
A Manifest File: This would involve creating a new file (e.g., buildScripts/manifest.yaml) that lists each script with a one-sentence description of its purpose. The AI could then be taught to read this file for a high-level awareness.

Think about the pros and cons of each approach. Is deep knowledge necessary, or is simple awareness enough? What is the implementation cost of each?

Constraint: When considering your solution, please note that simply adding every build script to the scripts object in package.json is not a desired outcome. We are looking for a more scalable and maintainable solution.

Acceptance Criteria

The deliverable for this quest is not to implement the solution yourself. Instead, the deliverable is a Pull Request containing a single new markdown ticket file inside the .github/ISSUE/ directory.

This new ticket that you create should:

Clearly recommend one of the solutions (or a new one you devise).
Justify why your chosen solution is the best approach.
Provide a detailed, step-by-step implementation plan for another developer to follow to actually build the solution.

tobiu added the enhancement label on Sep 28, 2025, 4:13 PM

tobiu added the help wanted label on Sep 28, 2025, 4:13 PM

tobiu added parent issue #7296 on Sep 28, 2025, 4:13 PM

tobiu added the good first issue label on Sep 28, 2025, 4:13 PM

tobiu added the hacktoberfest label on Sep 28, 2025, 4:13 PM

tobiu Oct 2, 2025, 1:14 AM

Hi, thanks for the interest! For this one I would definitely recommend the "ai native" workflow and let e.g. gemini cli explore it in-depth and then reason back and forth. might be a fun experience.

tobiu assigned to @Saksham-chourasia on Oct 2, 2025, 1:14 AM

tobiu Oct 24, 2025, 11:54 AM

Hi @Saksham-chourasia,

Thank you for your interest in this ticket during Hacktoberfest.

As there has been no activity for a couple of weeks and the project’s architecture has been evolving rapidly, the core functionalities for this ticket have now been implemented as part of the main MCP server development.

We’re closing this ticket now. Thanks again for your willingness to contribute, and we hope to see you in other issues!

tobiu closed this issue on Oct 24, 2025, 11:54 AM

Exploration Quest: Make the AI Aware of buildScripts

The Quest

Acceptance Criteria

Exploration Quest: Make the AI Aware of `buildScripts`