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	7367
title	Create Script to Automate GitHub Issue Creation from Markdown Ticket
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfestai
assignees	ksanjeev284
createdAt	Oct 5, 2025, 12:39 PM
updatedAt	Oct 5, 2025, 3:28 PM
githubUrl	https://github.com/neomjs/neo/issues/7367
author	tobiu
commentsCount	4
parentIssue	7364
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Oct 5, 2025, 3:28 PM

Create Script to Automate GitHub Issue Creation from Markdown Ticket

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

Closed v11.0.0 enhancementhelp wantedgood first issuehacktoberfestai

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

The current workflow requires the project maintainer to manually create a GitHub issue after a markdown ticket file has been created. This is a tedious and error-prone step that can be fully automated. This ticket is to create a script that uses the GitHub CLI (gh) to read a local ticket file and create a corresponding GitHub issue.

Acceptance Criteria

Create a new build script (e.g., buildScripts/ai/createGhIssue.mjs).
The script must accept the file path to a markdown ticket as an argument.
It should parse the markdown file to extract the title from the frontmatter for the GitHub issue title.
It should use the rest of the markdown file's content (excluding frontmatter) as the body for the GitHub issue.
The script will use gh issue create --title "<title>" --body-file <file> to create the issue. A temporary file might be needed for the body.
The script should be added to package.json as npm run ai:create-gh-issue.

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

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

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

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

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

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

ksanjeev284 Oct 5, 2025, 12:43 PM

can you assign me

tobiu Oct 5, 2025, 12:48 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 @ksanjeev284 on Oct 5, 2025, 12:48 PM

ksanjeev284 Oct 5, 2025, 12:50 PM

Hi @tobiu sure I have joiuned the channel and will start working on it

tobiu Oct 5, 2025, 3:28 PM

ha, just noticed that the PR mentioned #7376 instead of #7367 (this one). almost closed the wrong ticket^^

thx again for the contribution! closing this one as resolved.

tobiu closed this issue on Oct 5, 2025, 3:28 PM