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	9277
title	Improve LocationNormalizer with missing cities and countries
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 24, 2026, 12:27 AM
updatedAt	Feb 24, 2026, 12:42 AM
githubUrl	https://github.com/neomjs/neo/issues/9277
author	tobiu
commentsCount	3
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 12:29 AM

Improve LocationNormalizer with missing cities and countries

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 24, 2026, 12:27 AM

Based on the current user dataset for the DevIndex app, many locations are failing to match an ISO country code. Examples include Zurich, Vienna, Palestine, and numerous other cities and countries.

This ticket aims to update apps/devindex/services/LocationNormalizer.mjs by expanding the cityMap and the regex-based country mappings using the top unmatched locations extracted from apps/devindex/resources/users.jsonl.

tobiu added the enhancement label on Feb 24, 2026, 12:27 AM

tobiu added the ai label on Feb 24, 2026, 12:27 AM

tobiu assigned to @tobiu on Feb 24, 2026, 12:27 AM

tobiu referenced in commit 2cb05af - "feat(devindex): Add extensive missing location mappings for LocationNormalizer (#9277)" on Feb 24, 2026, 12:29 AM

tobiu Feb 24, 2026, 12:29 AM

Input from Gemini 3.1 Pro:

✦ I have updated LocationNormalizer.mjs with extensive additions based on the unmatched locations extracted from users.jsonl.

Added missing city mappings like Zurich, Vienna, Dubai, Moscow, and various European/Asian/American tech hubs.

Added regex mappings for missing countries like Palestine, UAE, Lithuania, Estonia, and many others. These additions should greatly reduce the number of unmatched users in the DevIndex grids. Changes are pushed in 2cb05af98.

tobiu closed this issue on Feb 24, 2026, 12:29 AM

tobiu referenced in commit c6ecf6a - "feat(devindex): Add final missing location mappings from unmatched data analysis (#9277)" on Feb 24, 2026, 12:37 AM

tobiu Feb 24, 2026, 12:38 AM

Input from Gemini 3.1 Pro:

✦ Added a final pass of missing locations based on the script's output, including Ecuador, Saudi Arabia, Morocco, Kyoto, Athens, Québec, Groningen, Rennes, Darmstadt, Gurgaon, Saint Petersburg, and Turin. (pushed in c6ecf6a40)

tobiu referenced in commit e66f62f - "feat(devindex): Add cities with 4 or 5 matches & update users.jsonl via script (#9277)" on Feb 24, 2026, 12:42 AM

tobiu Feb 24, 2026, 12:42 AM

Input from Gemini 3.1 Pro:

✦ I've also added places down to 4 matching occurrences from the script output, including Detroit, Bellevue, Marseille, Sheffield, Amman, Hobart, New Orleans, Glasgow, Puerto Rico, Montpellier, Peking, Istanbul, Chengdu, Guangdong, Ghana, Brno, Sofia, Liverpool, Hangzhou, Portland, Málaga, Waterloo, and Göteborg.

The script was subsequently used to actually write the updated country codes to apps/devindex/resources/users.jsonl, completing the normalization flow.

Total matched: ~33.5k Total unmatched: ~3.5k (down from many thousands, with mostly junk remaining like earth, localhost, etc).

Changes pushed in e66f62f25.

tobiu referenced in commit 4c81f7c - "fix(devindex): Add NH to US state codes in LocationNormalizer (#9277)" on Feb 24, 2026, 12:45 AM