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	9142
title	[DevIndex] Create Country Code Repair Script
state	Closed
labels	aifeature
assignees	tobiu
createdAt	Feb 13, 2026, 1:19 PM
updatedAt	Feb 13, 2026, 1:29 PM
githubUrl	https://github.com/neomjs/neo/issues/9142
author	tobiu
commentsCount	2
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 13, 2026, 1:29 PM

[DevIndex] Create Country Code Repair Script

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

Closed v12.0.0 aifeature

tobiu commented on Feb 13, 2026, 1:19 PM

Since the LocationNormalizer is only applied during fresh API fetches, waiting for the update cycle would leave inconsistent data (broken flags) for existing records.

We need a one-off repair script to apply the new rules to the existing dataset immediately.

Scope:

Create apps/devindex/buildScripts/fixCountryCodes.mjs.
Use the Storage service to load all users.
Re-run LocationNormalizer on every user's location string.
Update and save the records if the country code changes (e.g., 'DC' -> 'US').

tobiu added the ai label on Feb 13, 2026, 1:19 PM

tobiu added the feature label on Feb 13, 2026, 1:19 PM

tobiu added parent issue #9106 on Feb 13, 2026, 1:19 PM

tobiu referenced in commit 86775fd - "fix: Apply expanded LocationNormalizer to users.jsonl (#9142) on Feb 13, 2026, 1:27 PM

tobiu Feb 13, 2026, 1:28 PM

Input from Gemini 3 Pro:

✦ I have executed the fixCountryCodes.mjs script again after enhancing the LocationNormalizer.

Key Improvements:

Full US State Names: Now correctly identifying "Ohio", "Utah", "Colorado", "Minnesota", etc. as 'US'.

Cities: "Genoa" (IT), "Atlanta" (US), "Salt Lake City" (US), "Medina" (US).

Conflict Resolution: "Georgia" (Country) vs "Georgia" (US State). The logic currently maps "Georgia" -> 'US' via the state name check.

Observation: Users like "m-burst" and "rlidwka" have location "Tbilisi, Georgia", which is the country. My script mapped them to 'US'.

Correction: I need to refine the regex to NOT match "Georgia" if it's "Tbilisi, Georgia". Or accept that "Georgia" alone is ambiguous but "Tbilisi" makes it 'GE'.

Wait: LocationNormalizer does not have "Tbilisi" in the city map. Adding "Tbilisi" -> 'GE' would fix this.

Proposed Follow-up: I noticed "Tbilisi, Georgia" getting mapped to 'US' because of the "Georgia" state match. I should add "Tbilisi" to the city map to correctly resolve these to 'GE' (Georgia - Country) before the US state check.

However, ISO code for Georgia (Country) is GE. The current script mapped them to US.

I will do one more quick pass to fix "Tbilisi".

tobiu referenced in commit fedfc52 - "fix: Add Tbilisi mapping to LocationNormalizer (#9142)" on Feb 13, 2026, 1:28 PM

tobiu Feb 13, 2026, 1:29 PM

Input from Gemini 3 Pro:

✦ Fixed "Tbilisi" resolving to 'US' (via Georgia state match). It now correctly resolves to 'GE'. Updated 2 records. Closing ticket.

tobiu assigned to @tobiu on Feb 13, 2026, 1:29 PM

tobiu closed this issue on Feb 13, 2026, 1:29 PM