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	7791
title	Refactor ContentComponent to use new highlight.js utilities
state	Closed
labels	enhancementairefactoring
assignees	tobiu
createdAt	Nov 18, 2025, 11:13 AM
updatedAt	Nov 18, 2025, 8:27 PM
githubUrl	https://github.com/neomjs/neo/issues/7791
author	tobiu
commentsCount	0
parentIssue	7788
subIssues	7789 Create a utility for highlight.js line numbers 7790 Create a universal ESM bundle for highlight.js
subIssuesCompleted	2
subIssuesTotal	2
blockedBy	[]
blocking	[]
closedAt	Nov 18, 2025, 8:27 PM

Refactor ContentComponent to use new highlight.js utilities

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

Closed v11.5.0 enhancementairefactoring

tobiu commented on Nov 18, 2025, 11:13 AM

With the creation of a universal highlight.js bundle (#7790) and a HighlightJsLineNumbers utility (#7789), we can now refactor Portal.view.learn.ContentComponent to use this new, unified, and synchronous approach.

This will remove the dependency on the main thread addon for highlighting and simplify the component's logic.

Plan

Once #7790 and #7789 are complete, refactor ContentComponent.mjs.
Remove all usages of Neo.main.addon.HighlightJS.
Import the new Neo.util.Highlight and Neo.util.HighlightJsLineNumbers utilities.
Change the processReadonlyCodeBlocks method to be synchronous, using the new utilities to process code blocks.
Create a new SCSS file resources/scss/src/util/Highlight.scss.
Move the styles from apps/portal/resources/lib/highlightjs-custom-github-theme.css and the line number styles into this new file.
Ensure the new SCSS file is imported and used by the portal application.
Remove the old CSS files (highlightjs-custom-github-theme.css, highlightjs-custom-dark-theme.css). The dark theme can be re-added later if needed, using SCSS variables.

tobiu added the enhancement label on Nov 18, 2025, 11:13 AM

tobiu added the ai label on Nov 18, 2025, 11:13 AM

tobiu added the refactoring label on Nov 18, 2025, 11:13 AM

tobiu added sub-issue #7789 on Nov 18, 2025, 11:13 AM

tobiu added sub-issue #7790 on Nov 18, 2025, 11:13 AM

tobiu added parent issue #7788 on Nov 18, 2025, 11:13 AM

tobiu cross-referenced by #7788 on Nov 18, 2025, 11:16 AM

tobiu assigned to @tobiu on Nov 18, 2025, 11:23 AM

tobiu cross-referenced by #7790 on Nov 18, 2025, 1:12 PM

tobiu referenced in commit 8f1d7b7 - "Refactor ContentComponent to use new highlight.js utilities #7791 & added Neo.util.HighlightJs" on Nov 18, 2025, 7:21 PM

tobiu referenced in commit 4d45226 - "#7791 theming" on Nov 18, 2025, 7:45 PM

tobiu referenced in commit 5132316 - "#7791 portal app: removed custom hljs resources, using our new util class now" on Nov 18, 2025, 8:22 PM

tobiu referenced in commit b0edcaa - "#7791 removed the highlightjs devDependency (not needed when cloning the repo)" on Nov 18, 2025, 8:27 PM

tobiu closed this issue on Nov 18, 2025, 8:27 PM