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	657
title	How to create a webworkers driven multithreading App - Part\_2
state	Closed
labels	Blog Post
assignees	tobiu
createdAt	Jun 1, 2020, 4:11 PM
updatedAt	Jun 27, 2020, 3:32 PM
githubUrl	https://github.com/neomjs/neo/issues/657
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 24, 2020, 2:05 PM

How to create a webworkers driven multithreading App - Part 2

Closed v1.2.14/archive-v1-2-14-chunk-1 Blog Post

tobiu commented on Jun 1, 2020, 4:11 PM

https://medium.com/swlh/how-to-create-a-webworkers-driven-multithreading-app-part-2-3c5b3c2d1adb?source=friends_link&sk=cf4b5c0e014fcfd6fc1d9845f4eb3097

tobiu added the Blog Post label on Jun 1, 2020, 4:11 PM

tobiu assigned to @tobiu on Jun 1, 2020, 4:11 PM

tobiu Jun 2, 2020, 11:07 PM

Last Chance to add wishes & ideas what to cover in part 2:

part 1: https://medium.com/@tobiasuhlig/how-to-create-a-webworkers-driven-multithreading-app-part-1-fa0cc78a4237?source=friends_link&sk=a10ca85002f5f9c3ee8c69f53c79d95f

So far on the agenda: stores / collections, routing, views like the helix, table(s), selection models, event driven communication, working more with the API.

tobiu cross-referenced by #747 on Jun 17, 2020, 12:01 PM

tobiu closed this issue on Jun 24, 2020, 2:05 PM