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	7441
title	Convert Component Test component/DateSelector.mjs to Playwright
state	Closed
labels	enhancementhelp wantedhacktoberfestai
assignees	tobiu
createdAt	Oct 10, 2025, 6:53 PM
updatedAt	Nov 4, 2025, 8:30 PM
githubUrl	https://github.com/neomjs/neo/issues/7441
author	tobiu
commentsCount	2
parentIssue	7435
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 4, 2025, 8:30 PM

Convert Component Test component/DateSelector.mjs to Playwright

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

Closed v11.0.0 enhancementhelp wantedhacktoberfestai

tobiu commented on Oct 10, 2025, 6:53 PM

IMPORTANT: Before starting, please read the parent epic in detail to understand the required architecture and testing patterns: https://github.com/neomjs/neo/issues/7435

This task is part of Phase 2 and is blocked by the completion of Phase 1 (Test Harness Setup).

This task is to migrate the component test for component/DateSelector.mjs from the Siesta test harness to the Playwright test runner.

Acceptance Criteria

Create a new test file at test/playwright/component/component/DateSelector.spec.mjs.
Follow the architectural guide outlined in the parent epic for component test migration.
The new test must cover all the functionality of the original Siesta test (test/components/files/component/DateSelector.mjs).
Ensure the new test runs successfully via the component test runner.

tobiu added the enhancement label on Oct 10, 2025, 6:53 PM

tobiu added the help wanted label on Oct 10, 2025, 6:53 PM

tobiu added parent issue #7435 on Oct 10, 2025, 6:53 PM

tobiu added the hacktoberfest label on Oct 10, 2025, 6:53 PM

tobiu added the ai label on Oct 10, 2025, 6:53 PM

Mahita07 Oct 11, 2025, 1:32 PM

@tobiu could you please assign this issue to me ?

tobiu Oct 11, 2025, 1:48 PM

Sure, for this one you should sync with @Aki-07, since he is working on the harness. Before the harness is completed, you can not start. If you want to work on something else right away, you could e.g. create a couple new unit testing subs.

Spontaneous ideas (each file would need its own ticket):

-   `Neo.util.Array`
-   `Neo.util.String`
-   `Neo.util.Date`
-   `Neo.util.Matrix`

tobiu assigned to @Mahita07 on Oct 11, 2025, 1:48 PM

tobiu unassigned from @Mahita07 on Nov 4, 2025, 8:30 PM

tobiu assigned to @tobiu on Nov 4, 2025, 8:30 PM

tobiu referenced in commit a7b185b - "Convert Component Test component/DateSelector.mjs to Playwright #7441" on Nov 4, 2025, 8:30 PM

tobiu closed this issue on Nov 4, 2025, 8:30 PM