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

Mahita07 commented on Oct 6, 2025, 7:37 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 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 has the changes required to add a new workflow in AGENTS.md on how to list issues and PRs using GitHub CLI.
Please find the issue here

Mahita07 commented on Oct 6, 2025, 7:39 PM

@tobiu Could you please review this PR ?

tobiu commented on Oct 8, 2025, 2:02 PM

small typo inside the title (7336 vs 7366), but easy to match :)

✦ You were right. Issue #7366, "ENABLE AGENT TO LIST GITHUB ISSUES AND PRS," is a perfect match for the changes in this pull request. The contributor likely just referenced the wrong ticket ID.

The PR successfully implements all acceptance criteria from the correct ticket:

It adds a new section to AGENTS.md detailing the use of gh issue list and gh pr list.

It provides clear guidance and best practices for the agent.

It includes examples of user prompts that should trigger these commands.

The documentation is well-written and structured. This PR is good to merge.

tobiu commented on Oct 8, 2025, 2:39 PM

FYI: https://github.com/neomjs/neo/commit/b177ba4a2971bacf136194a6a3d9fc8f858cc124 => your new content is not lost, just moved from the agents file into a new guide, which is now referenced inside the agents file.

title	Add new workflow to list issues and PRs using GitHub CLI
author	Mahita07
state	Merged
createdAt	Oct 6, 2025, 7:37 PM
updatedAt	Oct 8, 2025, 2:39 PM
closedAt	Oct 8, 2025, 2:02 PM
mergedAt	Oct 8, 2025, 2:02 PM
branches	`dev` ← `list-gh-issues-prs`
url	https://github.com/neomjs/neo/pull/7396