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	7471
title	Refactor: Implement Granular Playwright Test Configurations
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 12, 2025, 4:06 PM
updatedAt	Oct 12, 2025, 4:10 PM
githubUrl	https://github.com/neomjs/neo/issues/7471
author	tobiu
commentsCount	1
parentIssue	7435
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 12, 2025, 4:10 PM

Refactor: Implement Granular Playwright Test Configurations

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

Closed v11.0.0 enhancementai

tobiu commented on Oct 12, 2025, 4:06 PM

This task covers the architectural refactoring of the Playwright test setup to support multiple, independent test suites. The previous configuration was monolithic and would have led to conflicts between unit and component tests.

The following changes were implemented to create a robust and scalable testing structure:

Granular Config Files:
- test/playwright/playwright.config.unit.mjs was created to exclusively run headless unit tests.
- test/playwright/playwright.config.component.mjs was created to exclusively run browser-based component tests, which require a web server.
- The root test/playwright/playwright.config.mjs was updated to serve as a master config that runs all test suites.
Dedicated NPM Scripts:
- The following scripts were added to package.json to provide clear entry points for developers and CI:
  - npm run test-unit: Runs only unit tests.
  - npm run test-components: Runs only component tests.
  - npm test: Runs the full suite.
Isolated Output Directories:
- Each configuration now writes its results to a dedicated output directory to prevent conflicts:
  - Unit tests: test/playwright/test-results/unit/
  - Component tests: test/playwright/test-results/component/
  - Full suite: test/playwright/test-results/all/

This new structure provides a clear, conflict-free, and easy-to-use system for all Playwright-based testing.

tobiu assigned to @tobiu on Oct 12, 2025, 4:06 PM

tobiu added the enhancement label on Oct 12, 2025, 4:06 PM

tobiu added parent issue #7435 on Oct 12, 2025, 4:06 PM

tobiu added the ai label on Oct 12, 2025, 4:06 PM

tobiu referenced in commit bd3b69a - "Refactor: Implement Granular Playwright Test Configurations #7471" on Oct 12, 2025, 4:07 PM

tobiu Oct 12, 2025, 4:10 PM

FYI @Aki-07 , @Mahita07 I think we are getting close with making the epic more accessible to others. These infrastructure items are rough, even with ai support. I had to push back on Gemini very hard, several times.

I will grab the button test next for a real migration and check how it works.

tobiu closed this issue on Oct 12, 2025, 4:10 PM