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	8935
title	Feat: Yearly Breakdown Columns & Heatmap
state	Closed
labels	enhancementdesign
assignees	tobiu
createdAt	Feb 1, 2026, 4:59 PM
updatedAt	Feb 1, 2026, 5:11 PM
githubUrl	https://github.com/neomjs/neo/issues/8935
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 1, 2026, 5:11 PM

Feat: Yearly Breakdown Columns & Heatmap

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

Closed v12.0.0 enhancementdesign

tobiu commented on Feb 1, 2026, 4:59 PM

This task focuses on leveraging the Neo.mjs Grid's horizontal scrolling capabilities by adding yearly contribution columns (2025 down to 2010). This will visualize the "career arc" of contributors.

Requirements

Model Update: Update DevRank.model.Contributor to expose yearly data as top-level fields (e.g., y2025, y2024) mapping from the nested years object.
Grid Columns:
- Dynamically generate columns for the range 2025 down to 2010.
- Place these columns after the "Updated" column.
- Header: The Year (e.g., "2025").
- Cell Content: The contribution count.
- Heatmap Styling: Apply a CSS class or inline style to the cell background based on the value intensity:
  - 0: No color
  - 1-100: Low intensity
  - 100-1000: Medium intensity
  - 1000+: High intensity

Acceptance Criteria

The grid displays ~16 new columns for yearly data.
Horizontal scrolling works smoothly.
Cells are color-coded based on contribution volume.

tobiu added the enhancement label on Feb 1, 2026, 4:59 PM

tobiu added the design label on Feb 1, 2026, 4:59 PM

tobiu added parent issue #8930 on Feb 1, 2026, 4:59 PM

tobiu assigned to @tobiu on Feb 1, 2026, 5:00 PM

tobiu referenced in commit dbd237b - "feat: Yearly Breakdown Columns & Heatmap (#8935)" on Feb 1, 2026, 5:03 PM

tobiu referenced in commit 71466c5 - "fix: Resolve maximum call stack error in GridContainer (#8935)" on Feb 1, 2026, 5:10 PM

tobiu Feb 1, 2026, 5:10 PM

Input from Gemini 3 Pro:

✦ I have resolved the Maximum call stack size exceeded error.

Issue

The error was caused by a naming collision or recursion loop when using the method name createColumns while extending Neo.grid.Container. It's likely that the base class or its config system interacts with a method of this name, or the columns setter triggered a cycle.

Fix

Renamed createColumns to buildDynamicColumns to ensure a unique method name.

Verified that buildDynamicColumns is called within construct after super.construct.

Ensured the static columns config was removed (it was already overwritten in the previous file write, but verified).

The grid should now render correctly without infinite recursion.

tobiu closed this issue on Feb 1, 2026, 5:11 PM