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	9222
title	DevIndex: Refactor StatusToolbar layout for mobile responsiveness
state	Closed
labels	enhancementdesignai
assignees	tobiu
createdAt	Feb 21, 2026, 1:58 AM
updatedAt	Feb 21, 2026, 2:03 AM
githubUrl	https://github.com/neomjs/neo/issues/9222
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 2:03 AM

DevIndex: Refactor StatusToolbar layout for mobile responsiveness

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

Closed v12.0.0 enhancementdesignai

tobiu commented on Feb 21, 2026, 1:58 AM

The StatusToolbar in the DevIndex home view previously wrapped awkwardly on small mobile screens (like iPhone 12 portrait, 390px width). The layout pushed visible rows to a second line while trying to keep total contributions on the first line, leading to a broken and unreadable user interface during streaming.

This issue tracks the refactoring of the toolbar's layout to provide a robust, responsive 2-row layout on mobile devices without relying on DOM hacks (like dummy break components) or brittle CSS Grid constraints.

Changes:

Grouped the statistics labels (Total Contributions, •, Visible Rows) into a semantic Neo.container.Base with an hbox layout.
Reverted the main toolbar layout back to Flexbox (hbox with wrap: 'wrap').
Adjusted SCSS to ensure the semantic stats container properly drops to a second row as a single, unbroken unit when space is constrained.
Maintained the transparent background and right-alignment for the new stats container.
Cleaned up unused, single-purpose CSS classes from the component configurations.

tobiu added the enhancement label on Feb 21, 2026, 1:58 AM

tobiu added the design label on Feb 21, 2026, 1:58 AM

tobiu added the ai label on Feb 21, 2026, 1:58 AM

tobiu referenced in commit d150135 - "feat: Refactor DevIndex StatusToolbar layout for mobile responsiveness (#9222)" on Feb 21, 2026, 2:02 AM

tobiu assigned to @tobiu on Feb 21, 2026, 2:02 AM

tobiu Feb 21, 2026, 2:03 AM

Input from Gemini 3 Pro:

✦ Refactored the DevIndex StatusToolbar for better mobile responsiveness.

Grouped the statistics labels (Total Contributions, •, Visible Rows) into a semantic Neo.container.Base with an hbox layout.

Set the main toolbar layout back to Flexbox (hbox with wrap: 'wrap').

Adjusted SCSS to ensure the semantic stats container properly drops to a second row as a single, unbroken unit when space is constrained.

Maintained the transparent background and right-alignment for the new stats container.

Cleaned up unused, single-purpose CSS classes.

tobiu closed this issue on Feb 21, 2026, 2:03 AM