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	7868
title	Implement consistent error handling for Memory Core MCP tools
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Nov 22, 2025, 10:12 PM
updatedAt	Nov 22, 2025, 10:20 PM
githubUrl	https://github.com/neomjs/neo/issues/7868
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 22, 2025, 10:20 PM

Implement consistent error handling for Memory Core MCP tools

Closed v11.9.0/archive-v11-9-0-chunk-1 enhancementai

tobiu commented on Nov 22, 2025, 10:12 PM

The following tools in ai/mcp/server/memory-core/services/toolService.mjs lack top-level try-catch blocks to ensure a consistent error shape for the MCP server:

Services to Update:

MemoryService.mjs: addMemory, listMemories, queryMemories
SummaryService.mjs: deleteAllSummaries, listSummaries, querySummaries
DatabaseService.mjs: exportDatabase, importDatabase
DatabaseLifecycleService.mjs: startDatabase, stopDatabase

Required Error Shape:

{
    error  : 'Description of the error',
    message: error.message,
    code   : 'ERROR_CODE' // e.g., MEMORY_ADD_ERROR, DATABASE_EXPORT_ERROR
}

Note: SessionService.summarizeSessions already implements this pattern. HealthService.healthcheck handles errors internally to return a health status, but should be reviewed to ensure it doesn't throw raw exceptions.

Task: Wrap the logic of the listed methods in try-catch blocks and return the standardized error object on failure.