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	9039
title	Feat: Support .env token auth for DevRank Services
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 7, 2026, 10:01 PM
updatedAt	Feb 7, 2026, 10:06 PM
githubUrl	https://github.com/neomjs/neo/issues/9039
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 7, 2026, 10:06 PM

Feat: Support .env token auth for DevRank Services

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

Closed v12.0.0 enhancementai

tobiu commented on Feb 7, 2026, 10:01 PM

Update the DevRank GitHub service (apps/devrank/services/GitHub.mjs) to support authentication via environment variables (GH_TOKEN or GITHUB_TOKEN) using dotenv.

This ensures the services can run in environments where the gh CLI is not authenticated or installed, or when the user prefers using an .env file.

Plan:

Initialize dotenv in apps/devrank/services/cli.mjs to load the .env file from the project root.
Modify apps/devrank/services/GitHub.mjs method #getAuthToken to check process.env before attempting the gh CLI fallback.

References:

apps/devrank/services/GitHub.mjs
apps/devrank/services/cli.mjs
package.json (dotenv dependency)

tobiu added the enhancement label on Feb 7, 2026, 10:01 PM

tobiu added the ai label on Feb 7, 2026, 10:01 PM

tobiu added parent issue #8930 on Feb 7, 2026, 10:01 PM

tobiu assigned to @tobiu on Feb 7, 2026, 10:02 PM

tobiu referenced in commit 49b9d02 - "feat: Support .env token auth for DevRank Services (#9039)" on Feb 7, 2026, 10:05 PM

tobiu Feb 7, 2026, 10:05 PM

Input from Gemini 3 Pro:

✦ Implemented support for environment variable authentication in DevRank services.

Changes

CLI Initialization: apps/devrank/services/cli.mjs now initializes dotenv (with quiet: true) to load .env files from the project root.

Auth Logic: apps/devrank/services/GitHub.mjs now prioritizes process.env.GH_TOKEN or process.env.GITHUB_TOKEN before falling back to the gh CLI.

Verification

Services can now run in environments without gh CLI authentication if a token is provided via .env.

gh CLI fallback remains active for local development convenience.

Code committed to dev branch.

tobiu closed this issue on Feb 7, 2026, 10:06 PM