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	9150
title	DevIndex: Client-Side "Commits Only" Toggle & Total Commits Implementation
state	Closed
labels	enhancementaiperformance
assignees	tobiu
createdAt	Feb 14, 2026, 1:10 AM
updatedAt	Feb 14, 2026, 2:48 AM
githubUrl	https://github.com/neomjs/neo/issues/9150
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 14, 2026, 2:48 AM

DevIndex: Client-Side "Commits Only" Toggle & Total Commits Implementation

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

Closed v12.0.0 enhancementaiperformance

tobiu commented on Feb 14, 2026, 1:10 AM

Implement "Commits Only" mode entirely on the client side to avoid data bloat, leveraging Store caching and App Worker performance.

`GridContainer.mjs`

Modify afterSetCommitsOnly:
- Swap the dataField of the Total column between totalContributions and totalCommits instead of overwriting renderers.
- This leverages the Store's "Soft Hydration" (via doSort) to cache totalCommits values on the raw objects upon first access.
- Propagate commitsOnly state to this.footerToolbar.

`StatusToolbar.mjs`

Add commitsOnly_ reactive config.
Update updateRowsLabels to compute the "Total Contributions" sum based on the active mode:
- Default: Sum tc (Total Contributions).
- Commits Only: Sum cy (Commits Year Array) using reduce.

This ensures zero data payload increase while maintaining high runtime performance.

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

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

tobiu added the performance label on Feb 14, 2026, 1:10 AM

tobiu added parent issue #9106 on Feb 14, 2026, 1:10 AM

tobiu assigned to @tobiu on Feb 14, 2026, 2:38 AM

tobiu referenced in commit 5016084 - "feat(devindex): Implement client-side 'Commits Only' mode (#9150)" on Feb 14, 2026, 2:47 AM

tobiu Feb 14, 2026, 2:47 AM

Input from Gemini 3 Pro:

✦ I have implemented the client-side "Commits Only" mode.

Core Enhancements:

src/grid/column/Base.mjs:

Made dataField reactive to support generic updates (committed previously).

apps/devindex/view/home/GridContainer.mjs:

Refactored afterSetCommitsOnly to use generic dataField swapping.

Extracted regexes to module constants.

Simplified onSortColumn logic using regexContributionYear.

apps/devindex/view/home/StatusToolbar.mjs:

Implemented updateLabels with store.resolveField fallback for robust, client-side totals.

Dynamic label text ("Total Commits" vs "Total Contributions").

This resolution optimizes performance by avoiding data bloat and leveraging the framework's reactive architecture.

tobiu closed this issue on Feb 14, 2026, 2:48 AM