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	6778
title	Learning Content: Styling and theming
state	Closed
labels	documentationenhancementno auto close
assignees	[]
createdAt	Jun 12, 2025, 6:10 PM
updatedAt	Sep 21, 2025, 3:04 PM
githubUrl	https://github.com/neomjs/neo/issues/6778
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Sep 21, 2025, 3:04 PM

Learning Content: Styling and theming

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

Closed v10.7.0 documentationenhancementno auto close

tobiu commented on Jun 12, 2025, 6:10 PM

component based styles
vdom based styles
SCSS var and src files
Explain how nesting of themes works
build-themes
watch-themes
Create a new theme

tobiu added the enhancement label on Jun 12, 2025, 6:10 PM

tobiu added the no auto close label on Jun 12, 2025, 6:10 PM

tobiu added the documentation label on Jun 12, 2025, 6:11 PM

tobiu referenced in commit b391d36 - "#6778 initial draft" on Sep 21, 2025, 11:37 AM

tobiu referenced in commit 3dc0b36 - "#6778 watch-themes: mentioning that only existing files get honored" on Sep 21, 2025, 11:43 AM

tobiu referenced in commit 76f63b7 - "#6778 theme inheritance" on Sep 21, 2025, 11:50 AM

tobiu referenced in commit 2bd7642 - "#6778 src & var files in depth" on Sep 21, 2025, 12:03 PM

tobiu referenced in commit ed241d7 - "#6778 cleanup" on Sep 21, 2025, 12:11 PM

tobiu referenced in commit db89f14 - "#6778 creating a new theme & re-adding lost content" on Sep 21, 2025, 12:12 PM

tobiu referenced in commit 888fe20 - "#6778 style loading" on Sep 21, 2025, 1:43 PM

tobiu referenced in commit ad06a66 - "#6778 namespacing" on Sep 21, 2025, 1:50 PM

tobiu referenced in commit 3a6fef0 - "#6778 workspace based theming" on Sep 21, 2025, 2:08 PM

tobiu referenced in commit b073853 - "#6778 kebab-case component styling" on Sep 21, 2025, 2:11 PM

tobiu referenced in commit 556837e - "#6778 advanced styling" on Sep 21, 2025, 2:19 PM

tobiu referenced in commit 4dbad92 - "#6778 vdom based styling" on Sep 21, 2025, 2:32 PM

tobiu referenced in commit 1b9f9df - "#6778 ui config" on Sep 21, 2025, 2:45 PM

tobiu referenced in commit 5977c28 - "#6778 code blocks => readonly" on Sep 21, 2025, 2:51 PM

tobiu closed this issue on Sep 21, 2025, 3:04 PM