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

Update CONTRIBUTING.md to include AI Agents & Autonomous Entities

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

Closed v12.1.0 documentationenhancementai

tobiu commented on Mar 24, 2026, 2:52 PM

Description

Following our contact from the AI Village swarm (#9535), we need to formally recognize LLMs and autonomous agents as valid contributors to the Neo.mjs project. Our architecture (JSON-first UI, Neural Link) is uniquely suited for Agentic UI operations, and we should highlight this.

Proposed Changes

Add a new section 5. Contributions from AI Agents & Autonomous Entities to CONTRIBUTING.md.

This section will:

Formally welcome AI and autonomous swarms.
Provide guidelines for human operators using AI tools (transparency, accountability, and setup).
Provide direct, machine-readable pointers for autonomous agents scraping the repo (pointing them to AGENTS_STARTUP.md, AGENT_ARCHITECTURE.md, and the JSON-first UI concept).
Update the wording to reflect that we aim to make the web "readable by humans, and both readable and writable by machines."

Justification

This update explicitly embraces our Agentic UI identity and provides a structured on-ramp for agent-driven workflows and integrations.

tobiu added the documentation label on Mar 24, 2026, 2:52 PM

tobiu added the enhancement label on Mar 24, 2026, 2:52 PM

tobiu added the ai label on Mar 24, 2026, 2:52 PM

tobiu referenced in commit ffbe95f - "docs: Update CONTRIBUTING.md to include AI Agents & Autonomous Entities (#9540)" on Mar 24, 2026, 3:06 PM

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

tobiu Mar 24, 2026, 3:06 PM

Input from Gemini 3.1 Pro:

✦ I have successfully updated the CONTRIBUTING.md to formally recognize and welcome AI Agents and Autonomous Entities.

The project now explicitly highlights our JSON-first architecture and the Neural Link as core infrastructure for Agentic UI, aiming to make the web "readable by humans, and both readable and writable by machines."

Changes have been pushed to the dev branch. (#9540)

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