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	6578
title	Create a guide for LLMS
state	Closed
labels	enhancement
assignees	[]
createdAt	Mar 18, 2025, 10:51 AM
updatedAt	Mar 21, 2025, 5:21 PM
githubUrl	https://github.com/neomjs/neo/issues/6578
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 21, 2025, 5:21 PM

Create a guide for LLMS

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

Closed v8.32.0 enhancement

tobiu commented on Mar 18, 2025, 10:51 AM

Experiment to check if we can get a fresh session up to speed with following one guide.

tobiu added the enhancement label on Mar 18, 2025, 10:51 AM

tobiu referenced in commit e2188a8 - "Create a guide for LLMS #6578" on Mar 18, 2025, 11:01 AM

tobiu referenced in commit 3410019 - "#6578 clearer guidance path" on Mar 18, 2025, 11:18 AM

tobiu referenced in commit 4a697c9 - "#6578 more precise structure" on Mar 18, 2025, 12:03 PM

tobiu referenced in commit 6a263e5 - "#6578 notes, polishing" on Mar 18, 2025, 12:43 PM

tobiu referenced in commit d2c912f - "#6578 portal app walkthrough" on Mar 18, 2025, 2:20 PM

tobiu referenced in commit 052c7b5 - "#6578 more content" on Mar 18, 2025, 3:22 PM

tobiu referenced in commit 2511ed7 - "#6578 enforcing to open all links inside this guide" on Mar 18, 2025, 5:36 PM

tobiu referenced in commit 340d0b5 - "#6578 sharpening the content" on Mar 18, 2025, 9:38 PM

tobiu referenced in commit e309120 - "#6578 added the code.LivePreview to the guide" on Mar 18, 2025, 10:29 PM

tobiu referenced in commit bd87798 - "#6578 added the grid" on Mar 18, 2025, 11:04 PM

tobiu referenced in commit 0318edc - "#6578 view controllers addition" on Mar 18, 2025, 11:36 PM

tobiu referenced in commit 56d5a56 - "#6578 highlight the importance of Neo.setupClass()" on Mar 18, 2025, 11:54 PM

tobiu referenced in commit 5ec29fd - "#6578 MessageChannels, RMA" on Mar 19, 2025, 12:13 AM

tobiu referenced in commit bdf0e71 - "#6578 MessageChannels, RMA" on Mar 19, 2025, 12:15 AM

tobiu referenced in commit 2ec59f2 - "#6578 npm dependencies" on Mar 19, 2025, 12:49 AM

tobiu referenced in commit b83cb23 - "#6578 history: making sure that there is the awareness that the neo dev-mode has full browser support. new section on forms." on Mar 19, 2025, 10:40 PM

tobiu referenced in commit 2b20f7b - "#6578 open link exception" on Mar 19, 2025, 10:51 PM

tobiu referenced in commit 72f024d - "#6578 forms polishing" on Mar 19, 2025, 11:17 PM

tobiu referenced in commit 505b754 - "#6578 following grok's instructions to further polish the guide" on Mar 20, 2025, 12:37 AM

tobiu referenced in commit 46a7116 - "#6578 learning curve turning points" on Mar 20, 2025, 1:27 AM

tobiu referenced in commit aae8a0c - "#6578 slightly shortening the guide to fit google gemini's max length" on Mar 20, 2025, 1:56 AM

tobiu referenced in commit bc97909 - "#6578 cleanup" on Mar 20, 2025, 2:00 AM

tobiu closed this issue on Mar 21, 2025, 5:21 PM