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	207
title	Neo.Xhr: relative URLs inside the framework repo
state	Closed
labels	enhancementstale
assignees	tobiu
createdAt	Dec 30, 2019, 1:35 AM
updatedAt	Sep 28, 2024, 4:32 AM
githubUrl	https://github.com/neomjs/neo/issues/207
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Sep 28, 2024, 4:32 AM

Neo.Xhr: relative URLs inside the framework repo

Closed v7.9.1/archive-v7-9-1-chunk-1 enhancementstale

tobiu commented on Dec 30, 2019, 1:35 AM

This topic is a bit more complex:

Since all requests go through the data-worker, the base URL is 2 levels below the repo root.

in case we do use neo.mjs as a node_module, there is a check in place to reduce the 4 levels below the workspace to 2 (consistency) => #206

However, in case there are Neo.Xhr calls within the repo, we don't want to change the paths (e.g. inside the examples).

Since we are in strict mode, there is no way to know which class / file triggered the call (callee). I think we need another optional Neo.Xhr config like insideNeo to deal with those edge cases.

tobiu added the enhancement label on Dec 30, 2019, 1:35 AM

tobiu assigned to @tobiu on Dec 30, 2019, 1:35 AM

tobiu referenced in commit d703853 - "https://github.com/neomjs/neo/issues/207" on Jan 2, 2020, 12:28 PM