What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	docs(test-plan): add component-Video test plan (#7489)
author	ritikrikm
state	Merged
createdAt	Oct 14, 2025, 8:04 PM
updatedAt	Oct 15, 2025, 1:38 PM
closedAt	Oct 15, 2025, 1:38 PM
mergedAt	Oct 15, 2025, 1:38 PM
branches	`dev` ← `feat/test-plan-component-video-7489`
url	https://github.com/neomjs/neo/pull/7490

Merged

ritikrikm commented on Oct 14, 2025, 8:04 PM

What kind of change does this PR introduce?

Bugfix
Feature
Code style update
Refactor
Build-related changes
Other, please describe: Documentation (AI-Native test plan)

Does this PR introduce a breaking change? (check one)

Yes
[ x ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

[ x ] It's submitted to the dev branch, not the main branch
[ x ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information: This PR adds the AI-Native Cookbook test plan for Neo.component.Video.

Epic: Create Component Test Plans (Hacktoberfest Cookbook) #7475
Sub-issue: Create Test Plan for component.Video #7489
File: .github/ISSUE/ticket-cpm-test-component-video.md

Scope:

Inherited behaviours (hidden, cls, style, baseCls)
Component-specific behaviours (autoplay, controls, muted/inline, ghost toggle, afterSetUrl, play/pause, afterSetPlaying)
Edge cases (url changes, empty url, autoplay without url)

Notes:

Excludes non-component demo UI like theme toggle.

tobiu commented on Oct 15, 2025, 1:37 PM

Sorry for the delay. i actually wanted to review the PR with using our new github-workflow mcp server for the first time, but then ended up in a massive refactoring effort to get it "right": https://github.com/neomjs/neo/issues/7477

Still work in progress.

I will accept the PR. We could probably enhance the ticket a bit more, and change the url of an existing video to something else at run-time.

Out of the testing scope, but probably good to get an idea what neo can do with this widget: start playing the video, then click the move button: https://neomjs.com/examples/videoMove/index.html