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	9065
title	Feat: Persist Yearly Commits Array in DevRank Data
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Feb 9, 2026, 12:58 AM
updatedAt	Feb 9, 2026, 1:44 AM
githubUrl	https://github.com/neomjs/neo/issues/9065
author	tobiu
commentsCount	2
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 9, 2026, 1:00 AM

Feat: Persist Yearly Commits Array in DevRank Data

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

Closed v12.0.0 enhancement

tobiu commented on Feb 9, 2026, 12:58 AM

Refactor the Updater service to persist a secondary array containing only commit counts per year.

Current State: The users.json schema stores y: [int] which represents total contributions (commits + issues + PRs + reviews).

New State: Add a new field cy: [int] ("Commit Years") to store the specific commit counts. This data is already being fetched via the recent "Lightweight Counters" refactor (#9063), so we just need to capture and store it.

Task:

Update apps/devrank/services/Updater.mjs to aggregate commitsArr alongside yearsArr.
Add cy to the minified output object.
(Optional) Update Contributor model to map this new field.

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

tobiu referenced in commit cd03882 - "Feat: Persist Yearly Commits Array in DevRank Data (#9065)" on Feb 9, 2026, 12:59 AM

tobiu Feb 9, 2026, 1:00 AM

Input from Gemini 3 Pro:

✦ I have implemented the backend changes to persist the yearly commits array.

Changes in Updater.mjs:

Introduced commitsArr to track totalCommitContributions per year.

Added cy field to the minified user object, containing this array.

Now, every user updated will have both y (Total Contributions) and cy (Commits Only) arrays.

Example payload:
{
  "l": "tobiu",
  "tc": 29876,
  "fy": 2011,
  "y": [0, 0, ...], // Total
  "cy": [0, 0, ...] // Commits
}

tobiu assigned to @tobiu on Feb 9, 2026, 1:00 AM

tobiu added parent issue #8930 on Feb 9, 2026, 1:00 AM

tobiu closed this issue on Feb 9, 2026, 1:00 AM

tobiu Feb 9, 2026, 1:44 AM

Input from Gemini 3 Pro:

✦ I have completed the backend implementation for persisting the yearly commits array.

Changes:

Updated apps/devrank/services/Updater.mjs to extract totalCommitContributions from the GitHub GraphQL response.

Aggregated these counts into a new cy (Commit Years) array in the minified user object.

Verified that the users.json output now includes this field for updated records.

This data is now available for the frontend to consume.