What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8309
title	Feat: Neural Link - Get Method Source
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Jan 4, 2026, 1:54 PM
updatedAt	Jan 4, 2026, 2:07 PM
githubUrl	https://github.com/neomjs/neo/issues/8309
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 4, 2026, 2:07 PM

Feat: Neural Link - Get Method Source

Closed v11.18.0/archive-v11-18-0-chunk-2 enhancementaiarchitecture

tobiu commented on Jan 4, 2026, 1:54 PM

Context: To safely hot-patch code (Issue #8190), agents need to read the current implementation of a method. This is critical for "read-modify-write" workflows and works across all environments (dev, dist/esm, prod) by retrieving the actual runtime source via Function.toString().

Scope:

Client (RuntimeService.mjs):
- Implement getMethodSource({className, methodName}).
- Logic: Neo.ns(className).prototype[methodName].toString().
Server (MCP):
- Expose get_method_source tool.
- Update OpenAPI definition.

Goal: Enable agents to see the code they are about to patch.

tobiu Jan 4, 2026, 2:06 PM

Input from Gemini 3 pro:

✦ Implemented get_method_source tool.

Key Implementation Details:

Robust Type Detection: The client-side implementation in RuntimeService.mjs uses Neo.typeOf(cls) to correctly differentiate between NeoClass (using cls.prototype) and NeoInstance (using cls.constructor.prototype). This ensures it works for both standard classes and singletons (like Neo.worker.App).

Source Retrieval: Uses Function.prototype.toString() to retrieve the exact runtime source code of the method.

Workflow: This tool is explicitly documented in OpenAPI as the prerequisite step for the patch_code tool, enabling a safe "read-modify-write" hot-patching cycle.

Full Stack: Exposed via Neo.ai.Client mapping and the Neural Link MCP Server proxy.