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.

Neo.mjs - Self-Evolving Software Organism

unknown commented on Sep 14, 2023, 5:06 PM

Please make sure to read the Contributing Guidelines:

https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md

What kind of change does this PR introduce? (check at least one)

Bugfix
Feature
Code style update
Refactor
Build-related changes
Other, please describe:

Does this PR introduce a breaking change? (check one)

Yes
No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

It's submitted to the dev branch, not the master branch
When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

unknown commented on Sep 14, 2023, 5:14 PM

@tobiu there is an issue when firing the userChange event in the Text component that I couldn't solve. When the user changes the field manually, first the userChange is fired, right before the change event. Since the fireChangeEvent method is debounced and the change comes right after userChange, userChange is never emitted. You can test it with/without delayable to see the difference.

fix #4818

tobiu commented on Sep 14, 2023, 8:30 PM

hi deniz, looks nice, but i have an idea how to resolve the issues in a different way (separate timers).

closing the PR and will provide an alternative, which we should discuss afterwards.

title	Feature/user change event fix #4818
author	unknown
state	Closed
createdAt	Sep 14, 2023, 5:06 PM
updatedAt	Sep 18, 2023, 11:39 AM
closedAt	Sep 14, 2023, 8:30 PM
mergedAt
branches	`dev` ← `feature/user-change-event`
url	https://github.com/neomjs/neo/pull/4905