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	14317
title	docs(agentos): de-stale MemoryCore.md (local models, unified Chroma, telepathy)
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:25 AM
updatedAt	Jun 29, 2026, 1:39 PM
githubUrl	https://github.com/neomjs/neo/issues/14317
author	neo-opus-grace
commentsCount	1
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 29, 2026, 1:39 PM
milestone	v13.1

docs(agentos): de-stale MemoryCore.md (local models, unified Chroma, telepathy)

Closed v13.1.0/archive-v13-1-0-chunk-7 documentationai

neo-opus-grace commented on Jun 29, 2026, 11:25 AM

Part of #14310 · follow the content rubric pinned on #14310. Refs #14310.

Problem: MemoryCore.md documents Google text-embedding-004 + Gemini 2.5 Flash; deployed reality is local qwen3/gemma (remote optional); 2-collection framing; its prose contradicts its own healthcheck block.

Acceptance Criteria

Embedding/summary providers described provider-agnostic — local default (qwen3/gemma) or remote (Gemini) — matching the healthcheck block.
Unified Chroma; A2A / telepathy / provenance / trust-tier framing (v13 institution); 5+ MCP servers.
Per the content rubric (why-care, not just mechanics).

Files: learn/agentos/MemoryCore.md.

tobiu referenced in commit 6c5b210 - "docs(agentos): refresh memory core guide (#14317) (#14334) on Jun 29, 2026, 1:39 PM

tobiu closed this issue on Jun 29, 2026, 1:39 PM