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	9111
title	Support ISO 2 country codes in CountryFlag component and grid column
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 12, 2026, 10:12 AM
updatedAt	Feb 12, 2026, 11:41 AM
githubUrl	https://github.com/neomjs/neo/issues/9111
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 11:41 AM

Support ISO 2 country codes in CountryFlag component and grid column

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 12, 2026, 10:12 AM

Support ISO 2 country codes in CountryFlag component and grid column.

src/component/CountryFlag.mjs:
- Add countryCode_ reactive config.
- Update afterSetLocation logic to prioritize countryCode for flag URL generation if available.
- Use location for the text label.
src/grid/column/CountryFlag.mjs:
- Add contentField config (defaulting to 'location').
- Update applyRecordConfigs to map countryCode from the record if available.
apps/devindex/view/home/GridContainer.mjs:
- Change the dataField for the 'Location' column from 'location' to 'country_code'.
- Set sortable: false for this column.

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

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

tobiu assigned to @tobiu on Feb 12, 2026, 10:15 AM

tobiu added parent issue #9106 on Feb 12, 2026, 10:15 AM

tobiu referenced in commit 3e60dfb - "feat: Implement ISO country filtering in DevIndex and fix Store Turbo Mode filtering (#9111)" on Feb 12, 2026, 11:40 AM

tobiu Feb 12, 2026, 11:41 AM

Input from Gemini 3 Pro:

✦ Implemented full support for ISO 2 country code filtering and rendering in DevIndex.

Framework Enhancements:

Neo.data.Store: Fixed a critical issue in Turbo Mode (autoInitRecords: false) where filtering during streaming (insertion) failed because raw data objects (POJOs) were not hydrated with mapped fields. Overridden isFilteredItem to resolve filter properties on the fly.

Neo.component.CountryFlag: Added countryCode_ and resolveCountryCode_ configs to support direct ISO code rendering without relying on location string parsing.

Neo.grid.column.CountryFlag: Added contentField config to separate the flag source (dataField) from the text label source.

App Implementation:

Store: Switched Contributors store to filter by country_code using exact match (===) instead of loose location search.

View: Updated GridContainer to use country_code for the Location column. Updated ControlsContainer to bind the Country combo to country_code and return the ISO code (valueField: 'code').

Logic: Ensured filter values are uppercased to match ISO standards in the data.

Verified that both initial loading with URL parameters and manual filtering now work correctly with the streaming grid.

tobiu closed this issue on Feb 12, 2026, 11:41 AM