What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	7976
title	Update MCP server config paths to use process.cwd()
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Dec 2, 2025, 3:50 PM
updatedAt	Dec 2, 2025, 3:59 PM
githubUrl	https://github.com/neomjs/neo/issues/7976
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Dec 2, 2025, 3:58 PM

Update MCP server config paths to use process.cwd()

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.15.0 enhancementai

tobiu commented on Dec 2, 2025, 3:50 PM

Updates the default configuration for the knowledge-base and memory-core MCP servers to resolve database and backup paths relative to process.cwd() instead of __dirname.

Why: Previously, paths were resolved relative to __dirname (the location of the config file inside the package).

In the Neo.mjs repo, this worked because the relative path ../../../../ pointed to the repo root.
In scaffolded apps (where Neo.mjs is a dependency in node_modules), this relative path resolved to the neo.mjs package root inside node_modules, causing databases and backups to be stored inside node_modules instead of the application workspace.

What: By using process.cwd(), we align with standard Node.js tooling behavior:

Dev Mode: Running from the Neo.mjs repo root places artifacts in the repo root.
App Mode: Running from a scaffolded app's root places artifacts in the app's root.

Changes:

ai/mcp/server/memory-core/config.mjs: Update memoryDb.path, memoryDb.backupPath, and sessionDb.backupPath.
ai/mcp/server/knowledge-base/config.mjs: Update path and dataPath.

tobiu added the enhancement label on Dec 2, 2025, 3:50 PM

tobiu added the ai label on Dec 2, 2025, 3:50 PM

tobiu assigned to @tobiu on Dec 2, 2025, 3:51 PM

tobiu closed this issue on Dec 2, 2025, 3:58 PM

tobiu Dec 2, 2025, 3:59 PM

Input from Gemini:

✦ I have implemented the path resolution changes.

Summary of Changes:

Updated ai/mcp/server/memory-core/config.mjs and ai/mcp/server/knowledge-base/config.mjs.

Replaced __dirname-based relative paths with process.cwd()-based absolute paths.

This ensures that databases and backups are correctly located in the workspace root (e.g., chroma-neo-memory-core) regardless of whether the server is run from the repo root or as a dependency in a scaffolded app.

Applied code formatting improvements (block alignment) to align with project standards.

The commit has been pushed.