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	8490
title	Harden and Refactor ChromaDB Defrag Tool
state	Closed
labels	enhancementairefactoringbuild
assignees	tobiu
createdAt	Jan 10, 2026, 1:47 AM
updatedAt	Jan 10, 2026, 1:59 AM
githubUrl	https://github.com/neomjs/neo/issues/8490
author	tobiu
commentsCount	3
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 1:55 AM

Harden and Refactor ChromaDB Defrag Tool

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

Closed v11.20.0 enhancementairefactoringbuild

tobiu commented on Jan 10, 2026, 1:47 AM

Improve the buildScripts/defragChromaDB.mjs tool to be more robust and enterprise-ready.

Changes:

Centralized Backups: Move backups to dist/chromadb-backups/<target>/ to avoid polluting the root directory.
Automated Cleanup: Implement a retention policy to delete backups older than 7 days, keeping at least the last 3.
Error Handling: Ensure the script exits with a non-zero code if any collection fails to restore, preventing false positives in CI/CD.
Config robustness: Ensure config loading handles missing paths gracefully or enforces a standard.

Goal: Provide a reliable maintenance tool for the AI infrastructure.

tobiu added the enhancement label on Jan 10, 2026, 1:47 AM

tobiu added the ai label on Jan 10, 2026, 1:47 AM

tobiu added the refactoring label on Jan 10, 2026, 1:47 AM

tobiu added the build label on Jan 10, 2026, 1:47 AM

tobiu assigned to @tobiu on Jan 10, 2026, 1:50 AM

tobiu referenced in commit d952600 - "feat: Harden ChromaDB defrag tool with backups and error tracking (#8490)" on Jan 10, 2026, 1:51 AM

tobiu Jan 10, 2026, 1:51 AM

Input from tobiu:

◆ Implemented enterprise-grade improvements to the ChromaDB defragmentation tool:

Centralized Backups: Backups are now stored in dist/chromadb-backups/<target>/ to prevent cluttering the root directory.

Retention Policy: Added automated cleanup to keep only the last 3 backups and delete those older than 7 days.

Error Handling: The script now tracks partial failures across collections and exits with a non-zero status code if any errors occur, ensuring better CI/CD integration.

Robustness: Added validation for database paths and configuration loading.

Refactoring complete.

tobiu referenced in commit 36f43ba - "fix: Add missing Neo import to defrag script to support config loading (#8490)" on Jan 10, 2026, 1:54 AM

tobiu Jan 10, 2026, 1:54 AM

Input from tobiu:

◆ Added a missing import Neo from '../src/Neo.mjs'; to buildScripts/defragChromaDB.mjs. This was necessary because the configuration files (ai/mcp/server/memory-core/config.mjs) rely on the global Neo namespace and Neo.setupClass, which are not available in a standalone Node.js script unless explicitly imported.

Verified by successfully running npm run ai:defrag-memory.

tobiu added the agent-task:completed label on Jan 10, 2026, 1:55 AM

tobiu Jan 10, 2026, 1:55 AM

Input from tobiu:

◆ Task complete. The defragChromaDB.mjs script is now robust, backup-enabled, and verified working. Closing.

tobiu closed this issue on Jan 10, 2026, 1:55 AM

tobiu removed the agent-task:completed label on Jan 10, 2026, 1:59 AM