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	9658
title	Enhance Memory-Core for explicit Gemma4 offline session summarization
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Apr 3, 2026, 2:31 PM
updatedAt	Apr 3, 2026, 3:48 PM
githubUrl	https://github.com/neomjs/neo/issues/9658
author	tobiu
commentsCount	1
parentIssue	9638
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 3, 2026, 3:20 PM

Enhance Memory-Core for explicit Gemma4 offline session summarization

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

Closedenhancementai

tobiu commented on Apr 3, 2026, 2:31 PM

The Memory-Core currently enforces Google Gemini logic internally for compiling summarization meta-blocks and indexing cognitive drift.

In pursuit of complete offline AI Swarm viability, this requirement should be configurable. We need to optionally route session summarizations through local Ollama models (such as gemma4), bypassing the Gemini upstream requirement where the offline topology proves capable enough.

Acceptance Criteria

Extend config.mjs in Memory Core with variables for local modelProvider and ollama endpoints.
Introduce polymorphic provider support into SessionService.mjs so it automatically maps prompt configurations through the correct REST pipeline (Ollama APIs vs Gemini SDK).
Draft a targeted Playwright suite mimicking five turns of dummy agent behavior, proving gemma4 can reliably intercept the summarization chain.
The unit suite must gracefully ignore/skip execution if gemma4 or the ollama daemon is unreachable.

tobiu added the enhancement label on Apr 3, 2026, 2:31 PM

tobiu added the ai label on Apr 3, 2026, 2:31 PM

tobiu referenced in commit 9aaf7ba - "feat: Extend SessionService generation model to support Ollama and Gemma 4 (#9658)" on Apr 3, 2026, 3:19 PM

tobiu Apr 3, 2026, 3:20 PM

Pushed in 9aaf7ba90. Playwright unit tests succeed successfully connecting to the local Ollama daemon for memory-core summarization.

tobiu closed this issue on Apr 3, 2026, 3:20 PM

tobiu referenced in commit 67d52ac - "test: Add dummy memory mock logic to offline summarization tests (#9658)" on Apr 3, 2026, 3:34 PM

tobiu assigned to @tobiu on Apr 3, 2026, 3:48 PM

tobiu added parent issue #9638 on Apr 3, 2026, 3:48 PM