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	7245
title	Implement AI Knowledge Base Support for Workspaces
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Sep 24, 2025, 2:47 AM
updatedAt	Sep 24, 2025, 2:54 AM
githubUrl	https://github.com/neomjs/neo/issues/7245
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Sep 24, 2025, 2:54 AM

Implement AI Knowledge Base Support for Workspaces

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

Closed v10.9.0 enhancement

tobiu commented on Sep 24, 2025, 2:47 AM

Task

Implement AI knowledge base support for a Neo.mjs workspace.

Scope

Extend the existing AI knowledge base functionality, currently implemented for the neo repository, to a generic workspace structure. This involved:

Modifying the create-app project:
- Updated create-app/tasks/createPackageJson.mjs to include the latest devDependencies from the neo repo and added alphabetically sorted ai:* scripts.
- Modified create-app/tasks/neo-app.mjs to copy AGENTS.md to the workspace root, create the chroma directory, and copy AI_QUICK_START.md to the workspace's .github folder.
- Updated create-app/tasks/createGitignore.mjs to include .env and chroma/ in the generated .gitignore file.
Adapting AI scripts within the neo repository:
- Refactored neo/buildScripts/ai/createKnowledgeBase.mjs, embedKnowledgeBase.mjs, and queryKnowledgeBase.mjs to use process.env.npm_package_name for the insideNeo check.
- Modified dotenv.config() calls in these scripts to dynamically load .env files from the correct location (either the neo repo root or two levels up for a workspace).
Establishing and applying formatting consistency:
- Agreed upon and applied a convention for column-based alignment in package.json files across the project, specifically re-formatting neo/package.json to adhere to this standard.

These changes ensure that newly generated Neo.mjs workspaces are fully equipped with AI knowledge base capabilities, including proper environment variable handling and documentation.

Goal

Enable AI agents to effectively use the knowledge base within any Neo.mjs workspace, improving their ability to understand and contribute to workspace-specific projects and reducing hallucination.

tobiu assigned to @tobiu on Sep 24, 2025, 2:47 AM

tobiu added the enhancement label on Sep 24, 2025, 2:47 AM

tobiu referenced in commit 5e4c824 - "Implement AI Knowledge Base Support for Workspaces #7245" on Sep 24, 2025, 2:53 AM

tobiu referenced in commit 5db3a8c - "counterpart for https://github.com/neomjs/neo/issues/7245" on Sep 24, 2025, 2:54 AM

tobiu closed this issue on Sep 24, 2025, 2:54 AM