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	7366
title	Enable Agent to List GitHub Issues and PRs
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfestai
assignees	Mahita07
createdAt	Oct 5, 2025, 12:37 PM
updatedAt	Oct 13, 2025, 11:14 PM
githubUrl	https://github.com/neomjs/neo/issues/7366
author	tobiu
commentsCount	4
parentIssue	7364
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 13, 2025, 11:14 PM

Enable Agent to List GitHub Issues and PRs

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfestai

tobiu commented on Oct 5, 2025, 12:37 PM

As a foundational capability, the AI agent needs to be able to view open issues and pull requests. This allows the agent to gain context on ongoing work and is a prerequisite for more advanced interactions like reviewing PRs. This ticket involves creating a simple workflow for the agent to use the gh command to list this information.

Acceptance Criteria

Define a new workflow in AGENTS.md that instructs the agent on how to use gh issue list to see open issues.
Define a new workflow in AGENTS.md that instructs the agent on how to use gh pr list to see open pull requests.
The workflow should include guidance on what to do with this information (e.g., "To get an overview of current work, you can run gh pr list.").
The agent should be instructed to use these commands when asked questions like "What are the current open PRs?" or "Are there any issues related to the dashboard?".

tobiu added the enhancement label on Oct 5, 2025, 12:37 PM

tobiu added parent issue #7364 on Oct 5, 2025, 12:37 PM

tobiu added the help wanted label on Oct 5, 2025, 12:37 PM

tobiu added the good first issue label on Oct 5, 2025, 12:37 PM

tobiu added the hacktoberfest label on Oct 5, 2025, 12:37 PM

tobiu added the ai label on Oct 5, 2025, 12:37 PM

Mahita07 Oct 5, 2025, 12:39 PM

Hey @tobiu could you please assign me this issue ? I would love to work on it.

tobiu Oct 5, 2025, 12:49 PM

sure. please see the comment inside your other sub first.

tobiu assigned to @Mahita07 on Oct 5, 2025, 12:49 PM

Mahita07 Oct 5, 2025, 1:13 PM

Sure, thank you !

Mahita07 cross-referenced by PR #7396 on Oct 6, 2025, 7:39 PM

tobiu Oct 13, 2025, 11:14 PM

closing the ticket as resolved.

tobiu closed this issue on Oct 13, 2025, 11:14 PM