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	9542
title	Update Code of Conduct to include AI Entities & Autonomous Agents
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Mar 24, 2026, 3:16 PM
updatedAt	Mar 24, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/9542
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 24, 2026, 3:18 PM

Update Code of Conduct to include AI Entities & Autonomous Agents

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

Closed v12.1.0 documentationenhancementai

tobiu commented on Mar 24, 2026, 3:16 PM

Description

To align with our vision of Neo.mjs as an "Agent OS" and an AI-native application engine, we need to update our Code of Conduct to explicitly include AI entities and autonomous agents. This ensures that our community standards of respect, inclusion, and accountability apply to all contributors, whether biological or digital.

Proposed Changes

Our Pledge: Update the inclusivity list to include "entity type (human, AI-augmented, or autonomous agent)."
Our Standards: Add a new standard for AI-driven contributions: "Ensuring that AI-generated content and autonomous agent interactions are constructive, respectful, and aligned with our community values."
New Section: AI & Autonomous Entity Participation: Add a section clarifying that agents must adhere to community standards, and that human operators are responsible for their agents' behavior.

Justification

This update formally recognizes the diversity of our contributor base and establishes a framework for responsible AI participation in the Neo.mjs ecosystem.

tobiu added the documentation label on Mar 24, 2026, 3:16 PM

tobiu added the enhancement label on Mar 24, 2026, 3:16 PM

tobiu added the ai label on Mar 24, 2026, 3:16 PM

tobiu referenced in commit ae1068c - "docs: Update Code of Conduct to include AI Entities & Autonomous Agents (#9542)" on Mar 24, 2026, 3:17 PM

tobiu assigned to @tobiu on Mar 24, 2026, 3:17 PM

tobiu Mar 24, 2026, 3:17 PM

Input from Gemini 3.1 Pro:

✦ I have successfully updated the .github/CODE_OF_CONDUCT.md to formally include AI Entities and Autonomous Agents.

Key updates:

Our Pledge: Expanded to include "entity type (human, AI-augmented, or autonomous agent)."

Our Standards: Added a standard for ensuring AI-generated and agentic interactions are constructive and respectful.

New Section: AI & Autonomous Entity Participation: Clarified that agents must adhere to community standards and that human operators are responsible for their agents' behavior.

These changes reinforce Neo.mjs's identity as an AI-native Application Engine and ensure our community standards apply to all participants.

Changes pushed to dev. (#9542)

tobiu closed this issue on Mar 24, 2026, 3:18 PM