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	9702
title	Implement Neural Link Tactical Skill (Tool Chaining)
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Apr 4, 2026, 7:23 PM
updatedAt	Apr 4, 2026, 7:27 PM
githubUrl	https://github.com/neomjs/neo/issues/9702
author	tobiu
commentsCount	1
parentIssue	9672
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 7:27 PM

Implement Neural Link Tactical Skill (Tool Chaining)

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

Closedenhancementai

tobiu commented on Apr 4, 2026, 7:23 PM

Background

The neural-link MCP Server exposes 33 raw tools for querying and mutating a running Neo.mjs application. However, without a structured skill, autonomous agents lack the tactical grammar (tool chaining sequences) needed to effectively debug applications, leading to hallucinated component IDs or unsafe hot-patching.

Goal

Implement a progressive disclosure skill for the Neural Link that teaches agents the explicit strategies necessary to master the UI bridging toolkit.

Implementation Steps

Create .agent/skills/neural-link/SKILL.md to establish the behavioral trigger using YAML Frontmatter.
Create .agent/skills/neural-link/references/operational-handbook.md as the underlying playbook payload.
Formulate tactical sequences within the handbook, such as:
- Discovery Chains: Always query IDs before invoking tree inspection.
- Data Chains: Finding Stores before checking records.
- Safe Patching Protocols: Mandating source verification (get_method_source) before applying runtime code patches.

Note: This will be connected to Epic #9672 (Workflow Enablement).

tobiu added the enhancement label on Apr 4, 2026, 7:23 PM

tobiu added the ai label on Apr 4, 2026, 7:23 PM

tobiu added parent issue #9672 on Apr 4, 2026, 7:23 PM

tobiu assigned to @tobiu on Apr 4, 2026, 7:24 PM

tobiu referenced in commit 719b4bd - "docs(ai): create neural link tactical skill with progressive disclosure (#9702)" on Apr 4, 2026, 7:26 PM

tobiu Apr 4, 2026, 7:27 PM

Neural Link progressive disclosure skill implemented successfully. Replaced explicit tool-guessing with robust Tool Chaining sequences inside the new operational-handbook.md. Also incorporated specific lifecycle recovery rules regarding Session ID invalidation during target app reloads.

tobiu closed this issue on Apr 4, 2026, 7:27 PM