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	7601
title	Create Dynamic OpenAPI Specification Generator for the MCP servers
state	Closed
labels	enhancementstaleai
assignees	[]
createdAt	Oct 22, 2025, 11:36 AM
updatedAt	Feb 5, 2026, 4:42 AM
githubUrl	https://github.com/neomjs/neo/issues/7601
author	tobiu
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 5, 2026, 4:42 AM

Create Dynamic OpenAPI Specification Generator for the MCP servers

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

Closed v12.0.0 enhancementstaleai

tobiu commented on Oct 22, 2025, 11:36 AM

Currently, our openapi.yaml files contain hardcoded values for defaults and constraints (e.g., default: 30, maximum: 100). While this provides valuable context to AI agents via the toolService, it has a significant drawback: the specification can become out of sync with the application's actual configuration.

If a user changes a default value in a config.mjs file, the agent, whose tools are derived from the static YAML file, will remain unaware of the new default. This creates a divergence between the documented behavior and the actual behavior.

The ideal solution is to make the OpenAPI specification itself dynamic. This ticket proposes creating a build script or server startup process that:

Reads a base openapi.yaml template.
Reads the relevant .mjs configuration files for each MCP server.
Injects the configuration values (e.g., defaults, limits) into the appropriate sections of the OpenAPI template.
Outputs a final, complete openapi.json or openapi.yaml file that is then used by the toolService and served to clients.

This will ensure that the tool definitions provided to AI agents are always a perfect reflection of the server's current configuration.

Acceptance Criteria

A new script is created (e.g., in ai/mcp/server/) to handle the generation of the OpenAPI specification.
The script correctly reads a template YAML file.
The script correctly reads the server configuration files.
The script merges the configuration values into the template to produce a final, valid OpenAPI specification.
The MCP server startup process is modified to either run this script or read the generated file, ensuring it always uses the dynamic spec.

tobiu added the enhancement label on Oct 22, 2025, 11:36 AM

tobiu added the ai label on Oct 22, 2025, 11:36 AM

SarthakJain29 Oct 23, 2025, 10:20 AM

Hey, Would love to work on this!

tobiu Oct 23, 2025, 2:43 PM

@SarthakJain29 Hi! Sorry, I did not flag this item as "low prio backlog". I would strongly recommend to pick a different one: not much to learn here (e.g. just wrapping yaml files into template literals and parsing the config vars), but the bigger problem is: the mcp server APIs are not stable yet => we will add more endpoints, fetch more fields etc., so it would just be a maintenance burden with frequent rewrites.

Feel free to ping me inside the slack / discord general channels => there are huge areas with higher impacts / more to learn / more fun to work on.

@github-actions - 2026-01-22T03:17:20Z

This issue is stale because it has been open for 90 days with no activity.

2026-01-22T03:17:21Z @github-actions added the stale label

@github-actions - 2026-02-05T03:42:32Z

This issue was closed because it has been inactive for 14 days since being marked as stale.

2026-02-05T03:42:33Z @github-actions closed this issue