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	7866
title	Bug: Prevent SessionService from summarizing the active session
state	Closed
labels	bugai
assignees	tobiu
createdAt	Nov 22, 2025, 9:54 PM
updatedAt	Nov 22, 2025, 10:04 PM
githubUrl	https://github.com/neomjs/neo/issues/7866
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 22, 2025, 10:04 PM

Bug: Prevent SessionService from summarizing the active session

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

tobiu commented on Nov 22, 2025, 9:54 PM

The summarizeSessions method in ai/mcp/server/memory-core/services/SessionService.mjs can inadvertently summarize the currently active session. This can happen in two scenarios:

Drift Detection: The findSessionsToSummarize method detects the current session as having a mismatch between DB memories and the summary (since the summary doesn't exist or is outdated), flagging it for summarization.
Manual Trigger: An agent manually calls the summarize_sessions tool with the current session ID or without arguments (triggering case 1).

Summarizing the active session is premature as the session is still ongoing. This leads to incomplete summaries and potentially multiple summary entries for the same session.

Goal: Add a guard clause in SessionService to explicitly exclude this.currentSessionId from being summarized, both when finding sessions automatically and when a specific sessionId is requested.

Task:

Modify SessionService.mjs (around line 291 in summarizeSessions) to filter out this.currentSessionId.