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	9801
title	[MCP] GitHub Workflow: Fix Discussion File Naming and Formatting
state	Closed
labels	bugai
assignees	tobiu
createdAt	Apr 9, 2026, 1:22 AM
updatedAt	Apr 9, 2026, 1:23 AM
githubUrl	https://github.com/neomjs/neo/issues/9801
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 9, 2026, 1:23 AM

[MCP] GitHub Workflow: Fix Discussion File Naming and Formatting

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

Closedbugai

tobiu commented on Apr 9, 2026, 1:22 AM

The Problem

When the GitHub Workflow SyncService synchronizes discussions to the local filesystem:

Discussion files are arbitrarily prefixed with only their number (e.g., 123.md), unlike tickets (issue-123.md) and releases (v1.0.0.md).
The generated markdown files have corrupted line endings containing literal \n strings rather than actual newline characters, breaking markdown rendering in text editors and viewers.

The Architectural Reality

Target Paths: ai/mcp/server/github-workflow/services/sync/DiscussionSyncer.mjs, ai/mcp/server/github-workflow/config.template.mjs, ai/mcp/server/github-workflow/config.mjs
Discussion File Prefixing: We will add discussionFilenamePrefix: 'discussion-' to the central AI configs and update DiscussionSyncer.mjs to use it, preventing bare-number file overlaps with future file types.
Corrupted Endings: In DiscussionSyncer.mjs, the markdown string generation manually appends \\n (double backslashes) instead of \n. It also incorrectly splits comment replies by \\n. We will refactor this string builder to use proper newline character interpolation, fixing the corrupted rendering upon sync.

Avoided "Gold Standards" / Traps

Avoided hardcoding file prefixes: Rather than strictly hardcoding 'discussion-' inside DiscussionSyncer.mjs, we maintain the framework's standard by injecting discussionFilenamePrefix into the centralized declarative configuration (config.template.mjs & config.mjs). This allows simple JSON overrides for alternative environments without hacking the server code.

tobiu added the bug label on Apr 9, 2026, 1:22 AM

tobiu added the ai label on Apr 9, 2026, 1:22 AM

tobiu referenced in commit 9a50354 - "fix: Update discussion file prefixing and formatting (#9801)" on Apr 9, 2026, 1:23 AM

tobiu assigned to @tobiu on Apr 9, 2026, 1:23 AM

tobiu Apr 9, 2026, 1:23 AM

Input from Antigravity (Gemini 3.1 Pro):

✦ Added discussionFilenamePrefix to the AI configurations and refactored the string builder in DiscussionSyncer.mjs to use proper \n newline character interpolation. This prevents raw integer filename collisions and fixes corrupted markdown rendering in the synced files. Implementation pushed and verified.

tobiu closed this issue on Apr 9, 2026, 1:23 AM