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

SarthakJain29 commented on Oct 5, 2025, 8:43 AM

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 main 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:

This PR continues the work on Issue #7345 – Agent Memory Reliability. After the Gemini AI agent identified missing intent-driven JSDoc in src/component/Circle.mjs, this update implements the suggested documentation improvements.

Changes

Added intent-driven JSDoc at the class level of Neo.component.Circle.

Included @summary tag and expanded description of the component’s purpose, layout, and interactivity.

Ensured formatting follows .github/CODING_GUIDELINES.md.

Linked Issue:

Fixes #7345

tobiu commented on Oct 5, 2025, 8:34 PM

my suspicion was right (comment on your other PR). to resolve the merge conflict, you will need to update your fork to be in sync with the dev branch again (there is a button inside the GH UI for it). then you can add another commit to this PR (your fork) and remove the deletion of the package-lock.json and change the ticket to an update (status: Done), or remove this file from the PR too.

SarthakJain29 commented on Oct 5, 2025, 8:47 PM

Thanks for pointing that out! I’ll make sure not to remove package-lock.json in upcoming PRs. I will update the fork and add another commit soon.

SarthakJain29 commented on Oct 6, 2025, 10:49 AM

Hey I had made the necessary changes to the PR, kindly review it whenever you get time. Thanks!

tobiu commented on Oct 6, 2025, 2:27 PM

let me see:

this is a merge conflict, but i will accept it, and afterwards re-generate the package.json.

title	Add intent-driven JSDoc for Neo.component.Circle
author	SarthakJain29
state	Merged
createdAt	Oct 5, 2025, 8:43 AM
updatedAt	Oct 6, 2025, 2:27 PM
closedAt	Oct 6, 2025, 2:27 PM
mergedAt	Oct 6, 2025, 2:27 PM
branches	`dev` ← `agent-jsdoc-circle-7345`
url	https://github.com/neomjs/neo/pull/7360