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	8346
title	Refactor DatabaseService to Config-based Opt-Out Auto-Sync
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 6, 2026, 1:45 AM
updatedAt	Jan 6, 2026, 2:10 AM
githubUrl	https://github.com/neomjs/neo/issues/8346
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 6, 2026, 2:10 AM

Refactor DatabaseService to Config-based Opt-Out Auto-Sync

Closed v11.19.0/archive-v11-19-0-chunk-1 enhancementai

tobiu commented on Jan 6, 2026, 1:45 AM

DatabaseService currently triggers an auto-sync/embed on startup. This is correct for the Server but needs to be disabled for CLI scripts to avoid double-runs.

Goal: Use KB_Config to allow scripts to Opt-Out of Auto-Sync.

Plan:

config.mjs: Add autoSync: true to the default configuration.
DatabaseService.mjs: Modify initAsync to check aiConfig.data.autoSync. If false, skip the sync logic.
ai/examples/sync_knowledge_base.mjs: Import config.mjs and set aiConfig.data.autoSync = false at the top level.

This maintains the "batteries included" behavior for the Server while allowing scripts to disable the side effect.

tobiu Jan 6, 2026, 2:09 AM

Input from Gemini 3 Pro:

✦ I have successfully refactored DatabaseService to use a Config-based "Opt-Out" strategy for Auto-Sync.

Changes Implemented:

ai/mcp/server/knowledge-base/config.mjs:

Added autoSync: true to the defaultConfig.

This ensures the MCP Server (and any default consumer) continues to auto-heal on startup.

ai/mcp/server/knowledge-base/services/DatabaseService.mjs:

Updated initAsync to check aiConfig.data.autoSync.

If false, the automatic syncDatabase() / embedKnowledgeBase() calls are skipped.

ai/services.mjs (SDK Entry Point):

Added KB_Config.data.autoSync = false at the top level.

This ensures that any script importing the AI SDK (e.g., agents, test runners) implicitly opts-out of the auto-sync behavior, preventing double-runs when they manage the database explicitly.

This solution centralizes the control, preserves "batteries-included" for the Server, and safely disables side effects for script execution.

tobiu cross-referenced by #8347 on Jan 6, 2026, 11:34 AM