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	7561
title	Refactor AI Config for Server-Specific Namespacing
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 20, 2025, 1:09 AM
updatedAt	Oct 20, 2025, 1:15 AM
githubUrl	https://github.com/neomjs/neo/issues/7561
author	tobiu
commentsCount	0
parentIssue	7536
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 20, 2025, 1:15 AM

Refactor AI Config for Server-Specific Namespacing

Closed v11.0.0/archive-v11-0-0-chunk-3 enhancementai

tobiu commented on Oct 20, 2025, 1:09 AM

The ai/mcp/server/config.mjs file currently mixes global and server-specific configurations at the top level. To improve clarity and scalability, we need to introduce server-specific namespaces.

This ticket covers refactoring the configuration for the memory-core server by creating a new memoryCore object. The existing memory and sessions configurations will be moved inside this new object and renamed for better clarity.

Acceptance Criteria

A new memoryCore object is added to the aiConfig in ai/mcp/server/config.mjs.
The existing memory config object is moved inside memoryCore and renamed to memoryDb.
The existing sessions config object is moved inside memoryCore and renamed to sessionDb.
All services within the ai/mcp/server/memory-core/ directory are updated to use the new configuration paths (e.g., aiConfig.memoryCore.memoryDb.port).
The memory-core server continues to function correctly after the refactoring.