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	9101
title	Fix: Standardize Font Awesome version usage in SCSS
state	Closed
labels	bugairefactoring
assignees	tobiu
createdAt	Feb 11, 2026, 11:16 AM
updatedAt	Feb 11, 2026, 11:18 AM
githubUrl	https://github.com/neomjs/neo/issues/9101
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 11, 2026, 11:18 AM

Fix: Standardize Font Awesome version usage in SCSS

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

Closed v12.0.0 bugairefactoring

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

I noticed an inconsistency in our Font Awesome usage.

package.json specifies "@fortawesome/fontawesome-free": "^7.1.0".
Some SCSS files use "Font Awesome 7 Free".
Some SCSS files (including the ones I just edited) use "Font Awesome 6 Free".
apps/devrank/index.html does NOT include a Font Awesome stylesheet link (it relies on the one injected by src/MicroLoader.mjs or similar mechanism, which usually defaults to FA5 or FA6 if not updated).

Tasks:

Verify what version of Font Awesome is actually being loaded in the browser.
Standardize the font-family usage in SCSS files to match the loaded version.
If we are indeed using FA7, update TreeList.scss and Viewport.scss to use "Font Awesome 7 Free".

Goal: Ensure consistent icon rendering and avoid mixing font versions.

tobiu added the bug label on Feb 11, 2026, 11:16 AM

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

tobiu added the refactoring label on Feb 11, 2026, 11:16 AM

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

tobiu Feb 11, 2026, 11:17 AM

Input from Gemini 3 Pro:

✦ I have conducted a thorough investigation into the Font Awesome versioning issue.

Findings:
package.json: Explicitly defines "@fortawesome/fontawesome-free": "^7.1.0".

all.min.css: The installed CSS file header confirms: * Font Awesome Free 7.1.0 by @fontawesome.
CSS Variable Definitions: The all.min.css file defines the font family as:
--_fa-family: var(--fa-family, var(--fa-style-family, "Font Awesome 7 Free"));
Inconsistency: The codebase currently contains a mix of "Font Awesome 6 Free" and "Font Awesome 7 Free". The recent changes to TreeList.scss and Viewport.scss incorrectly used version 6.
Resolution Plan: I will proceed with standardizing all Font Awesome font-family references to "Font Awesome 7 Free" to match the installed package and ensure consistent rendering. This applies to:

resources/scss/src/app/content/TreeList.scss

resources/scss/src/apps/legit/Viewport.scss

Any other discovered instances of version 6.

tobiu referenced in commit 5032bde - "fix: Standardize on Font Awesome 7 Free (#9101)" on Feb 11, 2026, 11:18 AM

tobiu Feb 11, 2026, 11:18 AM

Input from Gemini 3 Pro:

✦ I have standardized the Font Awesome version usage in the SCSS files.

Changes:

Updated resources/scss/src/app/content/TreeList.scss to use "Font Awesome 7 Free".

Updated resources/scss/src/apps/legit/Viewport.scss to use "Font Awesome 7 Free".

This aligns the CSS font-family definitions with the installed @fortawesome/fontawesome-free package (v7.1.0). The search for "Font Awesome 6 Free" now yields zero results in the resources/scss directory.

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

tobiu cross-referenced by #9100 on Feb 11, 2026, 11:21 AM