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	9289
title	[Enhancement] Refine AI Agent Ticket Workflow to ''Ticket-Before-Commit''
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 24, 2026, 12:11 PM
updatedAt	Feb 24, 2026, 12:25 PM
githubUrl	https://github.com/neomjs/neo/issues/9289
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 24, 2026, 12:25 PM

[Enhancement] Refine AI Agent Ticket Workflow to 'Ticket-Before-Commit'

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

Closed v12.0.0 documentationai

tobiu commented on Feb 24, 2026, 12:11 PM

Context The original "Ticket-First" mandate in AGENTS.md was overly rigid, demanding a ticket be created before any file modifications occurred. This hindered exploratory coding for complex bugs ("Unknown Unknowns") and often resulted in tickets with highly specific but ultimately incorrect proposed solutions, muddying the release notes.

The Problem If an agent rigidly creates a ticket proposing "Solution A" before investigating, and then discovers "Solution B" is required, the ticket body becomes misleading. Furthermore, the rigid gate discouraged the primary benefits of ticketing: precise task scoping and commit traceability.

The Solution Update the AGENTS.md protocol to the "Ticket-Before-Commit" Gate.

Emphasize that tickets should describe the problem, not necessarily the exact solution.
Explicitly allow local file modification and exploration to identify root causes.
Enforce the hard gate at the git commit stage to ensure traceability.
Strongly emphasize that tickets must be narrowly scoped to prevent bundled, unrelated changes in a single commit.

tobiu added the documentation label on Feb 24, 2026, 12:12 PM

tobiu added the ai label on Feb 24, 2026, 12:12 PM

tobiu assigned to @tobiu on Feb 24, 2026, 12:15 PM

tobiu Feb 24, 2026, 12:16 PM

Input from Gemini 3.1 Pro:

✦ The AGENTS.md file has been successfully updated.

The rigid "Ticket-First" mandate has been officially replaced with the "Ticket-Before-Commit" Gate. The new guidelines explicitly support exploratory coding for "Unknown Unknowns", emphasize problem-focused ticket descriptions to ensure clean release notes, and enforce the hard boundary at the git commit stage to maintain perfect traceability.

tobiu referenced in commit f2c401e - "docs(agents): Refine AI Agent Ticket Workflow to 'Ticket-Before-Commit' (#9289)" on Feb 24, 2026, 12:23 PM

tobiu closed this issue on Feb 24, 2026, 12:25 PM