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	7373
title	Define a Clear Pull Request Review Protocol for the Agent
state	Closed
labels	documentationenhancementhelp wantedgood first issuehacktoberfestai
assignees	LemonDrop847
createdAt	Oct 5, 2025, 1:33 PM
updatedAt	Oct 24, 2025, 11:46 AM
githubUrl	https://github.com/neomjs/neo/issues/7373
author	tobiu
commentsCount	3
parentIssue	7364
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 24, 2025, 11:46 AM

Define a Clear Pull Request Review Protocol for the Agent

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

Closed v11.0.0 documentationenhancementhelp wantedgood first issuehacktoberfestai

tobiu commented on Oct 5, 2025, 1:33 PM

With the agent being able to check out, diff, and comment on pull requests, it is crucial to have a clear, documented protocol for how it should conduct code reviews. This ensures the agent's feedback is consistent, constructive, and aligned with the project's standards. This ticket is to create that protocol within AGENTS.md.

Acceptance Criteria

A new "Pull Request Review Protocol" section is added to AGENTS.md.
The protocol must instruct the agent to always be constructive and polite in its feedback.
The protocol must require the agent to verify the PR against the project's .github/CODING_GUIDELINES.md.
The protocol must require the agent to run the project's tests (e.g., npm test) against the PR's code to check for regressions.
The protocol should define a standard format for review comments, e.g., starting with a summary of findings, followed by specific line-by-line comments.

tobiu added the documentation label on Oct 5, 2025, 1:33 PM

tobiu added parent issue #7364 on Oct 5, 2025, 1:33 PM

tobiu added the enhancement label on Oct 5, 2025, 1:33 PM

tobiu added the help wanted label on Oct 5, 2025, 1:33 PM

tobiu added the good first issue label on Oct 5, 2025, 1:33 PM

tobiu added the hacktoberfest label on Oct 5, 2025, 1:33 PM

tobiu added the ai label on Oct 5, 2025, 1:33 PM

LemonDrop847 Oct 5, 2025, 1:41 PM

Hi, Can I have a go at it?

tobiu Oct 5, 2025, 1:45 PM

Hi, and thanks for your interest.

These tickets require the "ai native" workflows, so you need to read these 2 first: https://github.com/neomjs/neo/blob/dev/.github/WORKING_WITH_AGENTS.md https://github.com/neomjs/neo/blob/dev/.github/AI_QUICK_START.md

Since the epic subs strongly build on and relate to each other, I also strongly recommend to join the Slack and / or Discord Channels, so that you guys can sync. Like a real project :)

https://join.slack.com/t/neomjs/shared_invite/zt-6c50ueeu-3E1~M4T9xkNnb~M_prEEOA https://discord.gg/6p8paPq

tobiu assigned to @LemonDrop847 on Oct 5, 2025, 1:45 PM

tobiu Oct 24, 2025, 11:45 AM

Hi @LemonDrop847,

Thank you for your interest in this ticket during Hacktoberfest.

As there has been no activity for over three weeks, we are closing this ticket. The definition of a PR review protocol is still a valid goal and will be revisited in the future.

Thanks again for your willingness to contribute!

tobiu closed this issue on Oct 24, 2025, 11:46 AM