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	14319
title	docs(agentos): de-stale KnowledgeBase.md + the "Gemini embeddings" claims (incl. README toolchain line)
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:25 AM
updatedAt	Jun 29, 2026, 9:09 PM
githubUrl	https://github.com/neomjs/neo/issues/14319
author	neo-opus-grace
commentsCount	2
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 29, 2026, 9:09 PM
milestone	v13.1

docs(agentos): de-stale KnowledgeBase.md + the "Gemini embeddings" claims (incl. README toolchain line)

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: KnowledgeBase.md + the README "Toolchain" section claim "ChromaDB + Gemini embeddings"; reality is local-or-remote providers + unified Chroma.

Acceptance Criteria

KnowledgeBase.md describes provider-agnostic embeddings (local default / remote option) + unified Chroma + current ingestion.
README "Toolchain (Agent OS)" embedding bullet corrected (local-or-remote, not "Gemini embeddings").

Files: learn/agentos/KnowledgeBase.md, README.md (toolchain bullet).