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	5429
title	tab.Container: getLayoutConfig() => replace the switch block with an object (map)
state	Closed
labels	enhancementgood first issuestale
assignees	[]
createdAt	Jun 21, 2024, 9:55 PM
updatedAt	Jan 15, 2025, 3:28 AM
githubUrl	https://github.com/neomjs/neo/issues/5429
author	tobiu
commentsCount	7
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2025, 3:28 AM

tab.Container: getLayoutConfig() => replace the switch block with an object (map)

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

Closed v8.5.0 enhancementgood first issuestale

tobiu commented on Jun 21, 2024, 9:55 PM

(No description provided)

tobiu added the enhancement label on Jun 21, 2024, 9:55 PM

tobiu added the good first issue label on Jun 21, 2024, 9:55 PM

TheCoderAdi cross-referenced by PR #5978 on Sep 29, 2024, 7:47 AM

TheCoderAdi Sep 29, 2024, 7:49 AM

Hello , I have added a pull request for it , Please review the changes and add a label for hacktoberfest2024

tobiu Sep 29, 2024, 1:10 PM

hi @TheCoderAdi!

the PR looks fine to me. I just took another look into the hacktoberfest rules, and if i understand them correctly, only PRs starting from October 1 count. If I am right on this one, you should re-send the PR on Tuesday, to ensure that you get the events credits.

Best regards, Tobias

TheCoderAdi Sep 29, 2024, 1:20 PM

Thank you for taking the time to review my PR! I really appreciate your feedback.

I'll hold off on any further pull/merge requests until October so they can count toward the event.

Looking forward to contributing once it starts!

Best regards, Aditya Swayamsiddha

On Sun, Sep 29, 2024, 4:41 PM Tobias Uhlig @.***> wrote:

hi @TheCoderAdi https://github.com/TheCoderAdi!

the PR looks fine to me. I just took another look into the hacktoberfest rules, and if i understand them correctly, only PRs starting from October 1 count. If I am right on this one, you should re-send the PR on Tuesday, to ensure that you get the events credits.

Best regards, Tobias

— Reply to this email directly, view it on GitHub https://github.com/neomjs/neo/issues/5429#issuecomment-2381315064, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2RBJLTSQUCOX4DNI2TFS7LZY7N4XAVCNFSM6AAAAABJWVH5HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBRGMYTKMBWGQ . You are receiving this because you were mentioned.Message ID: @.***>

2024-09-30T02:39:24Z @github-actions removed the stale label

TheCoderAdi cross-referenced by PR #5995 on Oct 1, 2024, 3:43 AM

TheCoderAdi Oct 1, 2024, 7:03 AM

I hope you're doing well! Since Hacktoberfest has officially started, I wanted to kindly request if you could merge the pull request I recently submitted. This will allow the contribution to count towards the event, and I'd be thrilled to see it make a positive impact.

Thank you for your time and support!

@github-actions - 2024-12-31T02:31:02Z

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

2024-12-31T02:31:02Z @github-actions added the stale label

@github-actions - 2025-01-15T02:28:58Z

This issue was closed because it has been inactive for 14 days since being marked as stale.

2025-01-15T02:28:59Z @github-actions closed this issue