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	19
title	Discussion: Nodejs & GraphQL based middleware
state	Closed
labels	enhancementhelp wantedepicstale
assignees	[]
createdAt	Nov 17, 2019, 5:28 PM
updatedAt	Oct 9, 2026, 10:01 PM
githubUrl	https://github.com/neomjs/neo/issues/19
author	tobiu
commentsCount	3
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 29, 2024, 4:39 AM

Discussion: Nodejs & GraphQL based middleware

Closed v7.9.1/archive-v7-9-1-chunk-1 enhancementhelp wantedepicstale

tobiu commented on Nov 17, 2019, 5:28 PM

Max (elmasse) brought up this topic:

We could set up a separate repository to create a neo.mjs middleware using nodejs & GraphQL.

Take a look at: https://graphql.org/graphql-js/

https://medium.com/codingthesmartway-com-blog/creating-a-graphql-server-with-node-js-and-express-f6dddc5320e1

This is an epic and probably involves a lot of work.

In short: neo.mjs should have a socket connection to the node server, probably using a custom API.

Schemas defined in the middleware could optionally automatically create models on the client side as well as the other way around. Changes to the data of a middleware schema should automatically update the store data of a bound client-side store as well as the other way around.

Would help for testing buffering of remotely loaded grids & tables.

I could definitely use feedback on this one!

tobiu added the enhancement label on Nov 17, 2019, 5:28 PM

tobiu added the help wanted label on Nov 17, 2019, 5:28 PM

tobiu added the epic label on Nov 17, 2019, 5:28 PM