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	7316
title	AI Knowledge Evolution
state	Closed
labels	enhancementepic
assignees	tobiu
createdAt	Oct 1, 2025, 10:51 PM
updatedAt	Oct 24, 2025, 11:53 AM
githubUrl	https://github.com/neomjs/neo/issues/7316
author	tobiu
commentsCount	2
parentIssue	null
subIssues	7317 Set up Memory ChromaDB 7318 Create Memory Capture API 7319 Create Memory Query Tool 7320 Update Agent Workflow for Memory 7321 Create Guide for Personalized Agent Identity 7322 Implement Memory Backup and Restore 7324 Refactor and Centralize AI Configuration 7325 Create Session Summarization API 7326 Document Optional Memory Core Setup 7332 Enhance Session Summary with Rich Metadata 7333 Create AI Strategic Workflows Guide 7334 Document Human Verification of Agent Memory 7335 Clarify Agent Memory Protocol and Tooling 7336 Implement Automated Session Summarization Workflow 7337 Enhance Agent Session Initialization: Generate New Session ID and Validate Memory Core State 7338 Implement Session Recovery Protocol in AGENTS.md 7341 Correct agent memory initialization protocol 7356 Clarify ai:add-memory command in AGENTS.md 7357 Create and Integrate `ai:get-last-session` Script 7358 Refactor `summarizeSession.mjs` to automatically summarize all un-summarized sessions 7361 Clarify Agent Memory Server Port in AGENTS.md 7362 Correct Agent Initialization Workflow 7363 Create `clearSummaries.mjs` script for development 7394 Clarify UUID Generation for Agent Memory 7397 Update AGENTS.md with Correct Health Check Endpoint 7398 Ensure Cross-Platform UUID Generation for Agent Memory
subIssuesCompleted	26
subIssuesTotal	26
blockedBy	[]
blocking	[]
closedAt	Oct 24, 2025, 11:53 AM

AI Knowledge Evolution

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

Closed v11.0.0 enhancementepic

tobiu commented on Oct 1, 2025, 10:51 PM

This epic outlines the plan to transform the AI agent from a stateless tool into a stateful, learning contributor with full accountability. The primary goal is to create a persistent, queryable memory for the agent that includes not only the "what" (code, docs) but also the "how" (conversations, decisions) and the "why" (internal thought process).

This will enable the agent to debug its own past work, understand the historical context of decisions, and improve its performance over time, making it a true partner in the development lifecycle.

This initiative is a key pillar for advanced workflows, alongside mandatory unit testing and roadmap-driven planning.

Top-Level Items & Implementation Phases

Phase 1: The Memory Core - A Unified History Database

Goal: Implement a persistent storage layer for all agent interactions.
Technology: Node.js and ChromaDB.

Phase 2: The Recall Engine - Integrating Memory into the Workflow

Goal: Enable the agent to query its own memory to inform its actions.

Phase 3: Personalized Agent Framework

Goal: Establish a framework for contributors to optionally configure a persistent memory and unique Git identity for their local AI agent.

tobiu assigned to @tobiu on Oct 1, 2025, 10:51 PM

tobiu added the enhancement label on Oct 1, 2025, 10:51 PM

tobiu added sub-issue #7317 on Oct 1, 2025, 10:52 PM

tobiu added sub-issue #7318 on Oct 1, 2025, 10:53 PM

tobiu added sub-issue #7319 on Oct 1, 2025, 10:55 PM

tobiu added sub-issue #7320 on Oct 1, 2025, 10:56 PM

tobiu added sub-issue #7321 on Oct 1, 2025, 11:11 PM

tobiu added the epic label on Oct 1, 2025, 11:30 PM

tobiu added sub-issue #7322 on Oct 1, 2025, 11:31 PM

tobiu referenced in commit d7db7b0 - "#7316 ticket md files" on Oct 1, 2025, 11:32 PM

tobiu added sub-issue #7324 on Oct 2, 2025, 10:41 AM

tobiu referenced in commit e53cf18 - "#7316 new sub md file" on Oct 2, 2025, 10:43 AM

tobiu added sub-issue #7325 on Oct 2, 2025, 11:50 AM

tobiu referenced in commit 8cc0055 - "#7316 new sub md file" on Oct 2, 2025, 11:52 AM

tobiu referenced in commit afe7ee9 - "#7316 mapping custom program versions to process.env.npm_package_version" on Oct 2, 2025, 2:00 PM

tobiu added sub-issue #7326 on Oct 2, 2025, 2:54 PM

tobiu added sub-issue #7332 on Oct 3, 2025, 10:41 AM

tobiu added sub-issue #7333 on Oct 3, 2025, 12:00 PM

tobiu added sub-issue #7334 on Oct 3, 2025, 12:15 PM

tobiu added sub-issue #7335 on Oct 3, 2025, 12:56 PM

tobiu added sub-issue #7336 on Oct 3, 2025, 1:16 PM

tobiu added sub-issue #7337 on Oct 3, 2025, 1:56 PM

tobiu added sub-issue #7338 on Oct 3, 2025, 2:13 PM

tobiu added sub-issue #7341 on Oct 4, 2025, 10:02 AM

tobiu cross-referenced by #7342 on Oct 4, 2025, 10:37 AM

tobiu cross-referenced by #7343 on Oct 4, 2025, 10:41 AM

tobiu cross-referenced by #7344 on Oct 4, 2025, 10:46 AM

tobiu cross-referenced by #7345 on Oct 4, 2025, 10:48 AM

tobiu cross-referenced by #7346 on Oct 4, 2025, 10:52 AM

tobiu Oct 4, 2025, 2:37 PM

some updates on the current progress:

tobiu added sub-issue #7356 on Oct 4, 2025, 2:38 PM

tobiu added sub-issue #7357 on Oct 4, 2025, 3:27 PM

tobiu added sub-issue #7358 on Oct 4, 2025, 7:49 PM

tobiu added sub-issue #7361 on Oct 5, 2025, 10:55 AM

tobiu added sub-issue #7362 on Oct 5, 2025, 11:50 AM

tobiu added sub-issue #7363 on Oct 5, 2025, 12:02 PM

tobiu added sub-issue #7394 on Oct 6, 2025, 3:29 PM

tobiu added sub-issue #7397 on Oct 7, 2025, 9:28 AM

tobiu referenced in commit 7bfbcb2 - "#7316 ticket md update" on Oct 7, 2025, 9:42 AM

tobiu added sub-issue #7398 on Oct 7, 2025, 9:51 AM

tobiu Oct 24, 2025, 11:53 AM

closing as resolved.

tobiu closed this issue on Oct 24, 2025, 11:53 AM