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	7568
title	Refine Issue Creation to be API-First
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 20, 2025, 1:26 PM
updatedAt	Oct 24, 2025, 11:31 AM
githubUrl	https://github.com/neomjs/neo/issues/7568
author	tobiu
commentsCount	1
parentIssue	7564
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 24, 2025, 11:31 AM

Refine Issue Creation to be API-First

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

Closed v11.0.0 enhancementai

tobiu commented on Oct 20, 2025, 1:26 PM

The current workflow for creating tickets involves manually creating a Markdown file, which is error-prone (e.g., using non-existent labels). We should flip this model to be API-first, using GitHub as the initial source of truth.

This ticket proposes creating a new create_issue tool within the github-workflow server. The agent will call this tool to create issues directly on GitHub, which will then be synced back to the local repository as Markdown files.

Acceptance Criteria

A new create_issue method is added to the IssueService in the github-workflow server.
This method uses gh issue create to create a new issue on GitHub, accepting parameters like title, body, labels, and assignees.
The openapi.yaml for the github-workflow server is updated to include the new create_issue tool.
Upon successful creation, the service should (ideally) trigger a sync to immediately pull the new issue down as a local .md file.
The agent workflow documented in AGENTS.md is updated to reflect that creating tickets should now be done via this new tool, not by manually creating files.

Benefits

Input Validation: Ensures all new tickets are valid at the point of creation (correct labels, assignees, etc.).
Simplified Agent Workflow: The agent interacts with a structured tool call instead of raw file creation.
Single Source of Truth: GitHub becomes the definitive source for new issue data.

tobiu assigned to @tobiu on Oct 20, 2025, 1:26 PM

tobiu added parent issue #7564 on Oct 20, 2025, 1:26 PM

tobiu added the enhancement label on Oct 20, 2025, 1:26 PM

tobiu added the ai label on Oct 20, 2025, 1:26 PM

tobiu Oct 24, 2025, 11:31 AM

resolved with the new tooling

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