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	9225
title	Handle GitHub IP allow list errors gracefully in Updater
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 21, 2026, 3:11 PM
updatedAt	Feb 21, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/9225
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 3:18 PM

Handle GitHub IP allow list errors gracefully in Updater

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 21, 2026, 3:11 PM

Some organizations on GitHub restrict access to their data via an "IP allow list". When the DevIndex Updater attempts to fetch contribution data for a user who belongs to such an organization, the GraphQL query fails with an "IP allow list enabled" error.

Currently, this causes the entire user update to fail, placing them in the "Penalty Box" (failed.json) for continuous, doomed retries.

Tasks:

Refine Error Handling in Updater.mjs: Inside the fetchUserData method, specifically within the year-by-year fallback loop, catch errors containing the phrase "IP allow list enabled".
Graceful Degradation: Instead of throwing the error and failing the user update, log a warning and continue. This will effectively treat the blocked year(s) as having 0 contributions (or missing data) but allow the rest of the user's profile and unblocked years to be successfully processed and saved.
This prevents these users from clogging the retry queue while still capturing their public metrics.

tobiu added the enhancement label on Feb 21, 2026, 3:11 PM

tobiu added the ai label on Feb 21, 2026, 3:11 PM

tobiu referenced in commit fb2a9a5 - "feat(devindex): Handle GitHub IP allow list errors gracefully to preserve public contributions (#9225)" on Feb 21, 2026, 3:18 PM

tobiu assigned to @tobiu on Feb 21, 2026, 3:18 PM

tobiu Feb 21, 2026, 3:18 PM

Input from Gemini 3 Pro:

✦ I have implemented the graceful degradation logic for IP Allow List errors.

GitHub.mjs: Added error detection inside the query method. When an "IP allow list enabled" error is caught from the GraphQL response, the client now logs a warning but returns the partial json.data (which contains the public contributions) instead of throwing a fatal error.

Updater.mjs: Inside the fetchUserData fallback loop, any secondary exceptions containing the "IP allow list" error string are now caught and skipped via a continue statement, ensuring that the entire update batch does not fail over one blocked year.

This ensures these users are successfully processed, their arrays remain sequentially intact (with 0 values automatically filling the restricted periods), and they avoid congesting the Penalty Box (failed.json). Changes pushed to dev. Closing.

tobiu closed this issue on Feb 21, 2026, 3:18 PM