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	7489
title	Create Test Plan for component.Video
state	Closed
labels	documentationhelp wantedgood first issuehacktoberfesttesting
assignees	tobiu
createdAt	Oct 14, 2025, 6:22 PM
updatedAt	Nov 15, 2025, 10:44 AM
githubUrl	https://github.com/neomjs/neo/issues/7489
author	tobiu
commentsCount	2
parentIssue	7475
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 15, 2025, 10:44 AM

Create Test Plan for component.Video

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

Closed v11.4.0 documentationhelp wantedgood first issuehacktoberfesttesting

tobiu commented on Oct 14, 2025, 6:22 PM

Your pull request should contain a single new file:

.github/ISSUE/ticket-cpm-test-component-video.md

This file will contain the test plan generated by following the cookbook.

How to Contribute

Read the Guide: Before you start, please read the main epic guide carefully:
- #7475
Request Assignment: If you would like to work on this ticket, please leave a comment here asking to be assigned.
Wait for Confirmation: Please wait for a project maintainer to confirm your assignment before you start working. This helps prevent multiple contributors from working on the same ticket.
Start your AI session: Once your assignment is confirmed, you can begin the work. Start your session with the AI agent by providing the local file paths for both this ticket and the main cookbook epic. This gives the agent the full context. For example:

"Hi Gemini, I am assigned to this ticket: @.github/ISSUE/ticket-component-testing-cookbook-component-video.md. Please use this cookbook as our guide: @.github/ISSUE/epic-cookbook-create-test-plans.md."
Follow the Cookbook: The cookbook epic will then guide you and the agent through the process of analyzing the component and generating the test plan.

tobiu assigned to @tobiu on Oct 14, 2025, 6:22 PM

tobiu added the documentation label on Oct 14, 2025, 6:22 PM

tobiu added the help wanted label on Oct 14, 2025, 6:22 PM

tobiu added the good first issue label on Oct 14, 2025, 6:22 PM

tobiu added the hacktoberfest label on Oct 14, 2025, 6:22 PM

tobiu added the testing label on Oct 14, 2025, 6:22 PM

tobiu added parent issue #7475 on Oct 14, 2025, 6:22 PM

tobiu cross-referenced by #7488 on Oct 14, 2025, 6:24 PM

ritikrikm Oct 14, 2025, 6:27 PM

Hi, you can assign me this. @tobiu Thanks

ritikrikm referenced in commit e84602f - "docs(test-plan): add component-Video test plan (#7489)" on Oct 14, 2025, 7:58 PM

ritikrikm cross-referenced by PR #7490 on Oct 14, 2025, 8:04 PM

tobiu referenced in commit 9c5115a - "docs(test-plan): add component-Video test plan (#7489)" on Oct 15, 2025, 1:38 PM

tobiu Nov 15, 2025, 10:44 AM

already resolved.

tobiu closed this issue on Nov 15, 2025, 10:44 AM