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	6033
title	examples/button/Base: opening the menu list does no longer allow using the arrow keys to navigate right away
state	Open
labels	bugepicno auto close
assignees	tobiu
createdAt	Oct 16, 2024, 12:45 AM
updatedAt	Jan 18, 2025, 10:36 PM
githubUrl	https://github.com/neomjs/neo/issues/6033
author	tobiu
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

examples/button/Base: opening the menu list does no longer allow using the arrow keys to navigate right away

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

Openbugepicno auto close

tobiu commented on Oct 16, 2024, 12:45 AM

looks like a regression bug to me. might be related to the main.addon.Navigator introduction
most likely just a missing focus() call

tobiu added the bug label on Oct 16, 2024, 12:45 AM

tobiu assigned to @tobiu on Oct 16, 2024, 12:45 AM

soumajit23 Oct 18, 2024, 9:18 AM

Hello @tobiu , I would like to work on this issue.

tobiu Oct 18, 2024, 11:10 AM

hi @soumajit23,

while contributions are welcome, i am afraid that this ticket is way too difficult for a first item to work on. you could easily spend a full week on it, since it requires in depth knowledge about the framework mechanics and change history.

My first thought was that it is related to @ThorstenRaab's commit, where he removed the focus() call when showing the button menu: https://github.com/neomjs/neo/commit/342afbbb50d82dd5b4c1230885b6933be9a40e85#diff-e2256fc11cf65d84943c3bd398132cb7e134ddba3a4af65cda9234874bf93b58R547

(i have no clue why this commit had no ticket and description, since it did breaks things)

digging deeper, it is definitely also related to @ExtAnimal's changes on selection models (separating selections and focus of items).

best regards, tobias

tobiu added the epic label on Oct 18, 2024, 11:10 AM

soumajit23 Oct 18, 2024, 11:49 AM

@tobiu thank you for clarifying! Looking into it, I see that it is definitely quite difficult to work on. I suppose I will look into other issues to work on for the time being.

@github-actions - 2025-01-17T02:27:36Z

This issue is stale because it has been open for 90 days with no activity.

2025-01-17T02:27:36Z @github-actions added the stale label

tobiu removed the stale label on Jan 18, 2025, 10:36 PM

tobiu added the no auto close label on Jan 18, 2025, 10:36 PM