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	7897
title	Index `test/playwright/` in Knowledge Base as raw source
state	Closed
labels	enhancementaitesting
assignees	tobiu
createdAt	Nov 24, 2025, 1:37 PM
updatedAt	Nov 24, 2025, 2:07 PM
githubUrl	https://github.com/neomjs/neo/issues/7897
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 24, 2025, 2:02 PM

Index `test/playwright/` in Knowledge Base as raw source

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

Closed v11.10.0 enhancementaitesting

tobiu commented on Nov 24, 2025, 1:37 PM

Index `test/playwright/` in Knowledge Base as raw source

The test/playwright/ directory contains the automated testing suite. This content is vital for the AI agent to understand how to write and maintain tests for the framework.

Unlike the ai/ directory, this content:

Does NOT need to be in the public Docs App.
Does NOT follow the strict class-based structure required by JSDoc.
Should be indexed as raw source files with a new type: test.

Goal

Enhance DatabaseService.mjs to explicitly scan and index the test/playwright directory.

Tasks

Update ai/mcp/server/knowledge-base/openapi.yaml to include test as a valid type enum for the query_documents tool.
Modify ai/mcp/server/knowledge-base/services/DatabaseService.mjs to:
- Implement a indexRawDirectory method (or similar) to scan a directory recursively.
- Call this method for test/playwright during the createKnowledgeBase process.
- Assign the type: 'test' to these chunks.
- Note: There are no node_modules inside test/playwright, so no exclusion is needed for that.

tobiu added the enhancement label on Nov 24, 2025, 1:37 PM

tobiu added the ai label on Nov 24, 2025, 1:37 PM

tobiu added the testing label on Nov 24, 2025, 1:37 PM

tobiu assigned to @tobiu on Nov 24, 2025, 2:00 PM

tobiu referenced in commit 861b526 - "Index test/playwright/ in Knowledge Base as raw source #7897" on Nov 24, 2025, 2:01 PM

tobiu closed this issue on Nov 24, 2025, 2:02 PM

tobiu Nov 24, 2025, 2:07 PM

Input from Gemini:

✦ The implementation is complete and verified.

Changes:

Documentation (ai directory):

Modified buildScripts/docs/jsdocx.mjs to include ai/**/*.mjs.

Added logic to correctly map the ai directory to the Neo.ai namespace in the JSDoc output.

Fixed multiple invalid JSDoc type definitions in AI services to ensure successful parsing.

Verified that docs/output/all.json now contains Neo.ai entries.

Tests (test/playwright directory):

Updated ai/mcp/server/knowledge-base/openapi.yaml to add test as a valid query type.

Enhanced DatabaseService.mjs with indexRawDirectory to scan and index the test/playwright folder as raw source files with type: 'test'.

Verification:

A Knowledge Base sync was performed using the Code Execution pattern (sync_knowledge_base.mjs).

Manual testing in a parallel session confirmed that queries with type: 'test' correctly return relevant Playwright specs (e.g., test/playwright/unit/button/Base.spec.mjs for query "button").

The Knowledge Base now covers the SDK, MCP servers, and the automated testing suite.