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	7371
title	Enable Agent to Diff a Pull Request
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfestai
assignees	pranjalarora98
createdAt	Oct 5, 2025, 1:22 PM
updatedAt	Oct 24, 2025, 11:43 AM
githubUrl	https://github.com/neomjs/neo/issues/7371
author	tobiu
commentsCount	3
parentIssue	7364
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 24, 2025, 11:43 AM

Enable Agent to Diff a Pull Request

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfestai

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

After checking out a PR branch, the agent needs a way to see the changes introduced by the pull request. The gh pr diff command is a straightforward way to get a summary of the changes. This ticket is to create a workflow for the agent to use this command.

Acceptance Criteria

A new workflow is added to AGENTS.md.
The workflow instructs the agent on how to use gh pr diff <PR_NUMBER> to view the changes in a pull request.
The agent should be instructed to use this command after checking out a PR branch to get an overview of the changes before doing a more detailed file-by-file review.

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

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

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

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

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

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

pranjalarora98 Oct 5, 2025, 2:43 PM

@tobiu can u plz assign. Me this!!!

tobiu Oct 5, 2025, 4:13 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

For this specific sub, there is a strict requirement to have https://github.com/neomjs/neo/issues/7370 finished first (blocker).

More input from Gemini:

✦ Yes, your assumption is exactly right.

The ticket ticket-agent-can-diff-a-pr.md is directly dependent on ticket-agent-can-checkout-pr-branch.md.

The description in the "diff" ticket explicitly states the intended sequence: "After checking out a PR branch, the agent needs a way to see the changes...".

To build a coherent workflow for me to follow, the instructions must be created in logical order. I need to be taught how to get the code (checkout) before I can be taught how to inspect the changes (diff).

Recommendation: Work on ticket-agent-can-checkout-pr-branch.md should be completed before work begins on ticket-agent-can-diff-apr.md.

tobiu assigned to @pranjalarora98 on Oct 5, 2025, 4:13 PM

tobiu Oct 24, 2025, 11:42 AM

Hi @pranjalarora98,

Thank you for your interest in this ticket during Hacktoberfest.

The functionality described in this ticket has now been implemented and superseded by the 'get_pull_request_diff' tool in the new GitHub Workflow MCP server. This tool was used to review all open PRs during the session where this ticket was closed.

We're closing this ticket as it has been resolved. Thanks again for your willingness to contribute!

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