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	9100
title	Perf: Remove unused Material Icons from Portal index.html
state	Closed
labels	enhancementaiperformance
assignees	tobiu
createdAt	Feb 11, 2026, 11:04 AM
updatedAt	Feb 11, 2026, 11:21 AM
githubUrl	https://github.com/neomjs/neo/issues/9100
author	tobiu
commentsCount	2
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 11, 2026, 11:21 AM

Perf: Remove unused Material Icons from Portal index.html

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

Closed v12.0.0 enhancementaiperformance

tobiu commented on Feb 11, 2026, 11:04 AM

After verifying that the apps/portal codebase and its associated SCSS files do not contain any references to "material-icons", we can safely remove the Google Fonts link for Material Icons from apps/portal/index.html.

Goal: Remove the unused Material Icons dependency to improve page load performance.

Verification: grep searches across apps/portal and resources/scss confirmed zero usage.

tobiu added the enhancement label on Feb 11, 2026, 11:04 AM

tobiu added the ai label on Feb 11, 2026, 11:04 AM

tobiu added the performance label on Feb 11, 2026, 11:04 AM

tobiu added parent issue #8930 on Feb 11, 2026, 11:05 AM

tobiu Feb 11, 2026, 11:12 AM

Input from Gemini 3 Pro:

✦ I incorrectly assumed Material Icons were unused because of a case-sensitive grep mismatch ("material-icons" vs "Material Icons"). The TreeList.scss component, shared by Portal and DevRank, explicitly sets font-family: 'Material Icons'.

Revised Plan:

Refactor resources/scss/src/app/content/TreeList.scss to use FontAwesome instead of Material Icons.

Replace \e5cc (Chevron Right) with \f054 (FontAwesome fa-chevron-right).

Replace \e5cf (Chevron Down) with \f078 (FontAwesome fa-chevron-down).

Update font-family to "Font Awesome 6 Free".

Ensure font-weight: 900 is set (required for FA solid icons).

Also fix resources/scss/src/apps/legit/Viewport.scss which has the same issue.

This will allow us to keep the removal of the Material Icons dependency from index.html.

tobiu assigned to @tobiu on Feb 11, 2026, 11:16 AM

tobiu Feb 11, 2026, 11:21 AM

Input from Gemini 3 Pro:

✦ I have resolved this issue as part of the broader work in #9101 ("Fix: Standardize Font Awesome version usage in SCSS").

Resolution: The Material Icons dependency was removed from apps/portal/index.html as planned. The visual assets (Chevron icons in the TreeList) that were relying on it have been migrated to FontAwesome 7 Free, eliminating the need for the Material Icons font file.

This ensures both the performance gain (fewer requests) and visual consistency.

tobiu closed this issue on Feb 11, 2026, 11:21 AM