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	7235
title	Refine AI Agent Guidelines for Query-Driven Comments
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Sep 23, 2025, 1:49 PM
updatedAt	Sep 23, 2025, 1:50 PM
githubUrl	https://github.com/neomjs/neo/issues/7235
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Sep 23, 2025, 1:50 PM

Refine AI Agent Guidelines for Query-Driven Comments

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

Closed v10.8.0 enhancement

tobiu commented on Sep 23, 2025, 1:49 PM

Description

The AGENTS.md file, which serves as the constitution for AI agents, was enhanced to improve the quality and discoverability of generated documentation.

Changes

The "Knowledge Base Enhancement Strategy" was renamed to "Contributing Queryable, Intent-Driven Comments" to better reflect its goal.
A new step, "Anticipate Future Queries," was added. This instructs agents to enrich class-level comments with conceptual keywords (e.g., reactivity, state management) to act as "semantic signposts" for the knowledge base search.
The documentation generation step was updated to mandate the use of structured JSDoc tags, specifically @summary for a concise overview and @see to link to related code or guides.
The example in the AGENTS.md file was updated to reflect this new, higher standard for query-driven comments.

Impact

This change formalizes a more advanced documentation strategy, ensuring that all future AI-driven documentation contributions will not only explain the code but also significantly improve the semantic richness and discoverability of the knowledge base.

tobiu assigned to @tobiu on Sep 23, 2025, 1:49 PM

tobiu added the enhancement label on Sep 23, 2025, 1:49 PM

tobiu changed title from Refine AGENTS.md for Enhanced Agent Workflow to Refine AI Agent Guidelines for Query-Driven Comments on Sep 23, 2025, 1:49 PM

tobiu referenced in commit f178a98 - "Refine AI Agent Guidelines for Query-Driven Comments #7235" on Sep 23, 2025, 1:50 PM

tobiu closed this issue on Sep 23, 2025, 1:50 PM