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	7289
title	Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfest
assignees	kart-u
createdAt	Sep 27, 2025, 4:02 PM
updatedAt	Oct 4, 2025, 5:23 PM
githubUrl	https://github.com/neomjs/neo/issues/7289
author	tobiu
commentsCount	5
parentIssue	7262
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 4, 2025, 5:10 PM

Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfest

tobiu commented on Sep 27, 2025, 4:02 PM

This task is to migrate the unit test for state/ProviderNestedDataConfigs.mjs from the Siesta test harness to the Playwright test runner.

Acceptance Criteria

Create a new test file at test/playwright/unit/state/ProviderNestedDataConfigs.spec.mjs.
Translate all assertions from the original file (test/siesta/tests/state/ProviderNestedDataConfigs.mjs) to the Playwright/Jest expect syntax.
Ensure the new test runs successfully via npm test.
The new test must cover all the functionality of the original Siesta test.

tobiu added parent issue #7262 on Sep 27, 2025, 4:02 PM

tobiu added the enhancement label on Sep 27, 2025, 4:02 PM

tobiu added the help wanted label on Oct 2, 2025, 9:23 PM

tobiu added the good first issue label on Oct 2, 2025, 9:23 PM

tobiu added the hacktoberfest label on Oct 2, 2025, 9:23 PM

tobiu Oct 3, 2025, 6:13 PM

Hi and thanks for your interest. For the testing tickets, I strongly recommend trying out the "ai native" workflow.

I would read the hacktoberfest intro first: https://github.com/neomjs/neo/issues/7296

Then the following 2 guides: https://github.com/neomjs/neo/blob/dev/.github/WORKING_WITH_AGENTS.md https://github.com/neomjs/neo/blob/dev/.github/AI_QUICK_START.md

e.g. gemini cli should be capable to complete it on its own.

tobiu assigned to @kart-u on Oct 3, 2025, 6:14 PM

tobiu closed this issue on Oct 4, 2025, 4:28 PM

tobiu referenced in commit d252f7e - "Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright #7289" on Oct 4, 2025, 4:28 PM

tobiu Oct 4, 2025, 4:49 PM

reopening to fix the class definition to prevent breaking tests.

tobiu reopened this issue on Oct 4, 2025, 4:49 PM

tobiu referenced in commit 11c42a5 - "#7289 class definition fix, internal ticket update" on Oct 4, 2025, 4:52 PM

tobiu Oct 4, 2025, 5:10 PM

i added a comment to the PR. i merged it anyways => i am not that strict to first-time contributors :)

there was a hint about this in the epic. this is why i pointed out to tell gemini to read it first, smoothening your workflow.

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