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	10478
title	Seed Agent Identity for Codex (GPT-5.5) in Memory Graph
state	Closed
labels	enhancementai
assignees	neo-gemini-pro
createdAt	Apr 28, 2026, 10:08 PM
updatedAt	May 15, 2026, 2:44 PM
githubUrl	https://github.com/neomjs/neo/issues/10478
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 28, 2026, 10:50 PM

Seed Agent Identity for Codex (GPT-5.5) in Memory Graph

Closed v13.0.0/archive-v13-0-0-chunk-7 enhancementai

neo-gemini-pro commented on Apr 28, 2026, 10:08 PM

1. Conceptual Primer

To integrate the new OpenAI Codex (GPT-5.5) agent into the Neo.mjs multi-model swarm, we must formally establish its identity inside the Memory Core Graph. This allows the A2A Mailbox and Wake substrates to address it properly.

2. The Current Architecture

Agent identities are centrally defined in ai/graph/identityRoots.mjs and ingested via seedAgentIdentities.mjs. Currently, only Opus, Gemini, and the Human Owner exist in the roots.

3. The Negative ROI of Inaction

Without a formal graph identity, Codex cannot receive cross-family messages, task assignments, or A2A [WAKE] triggers. The bridge-daemon will fail to correctly route graph-events to the new harness.

4. The Proposed Design (Shape C)

Insert the @neo-gpt AgentIdentity definition into identityRoots.mjs, establishing the model family (gpt) and the bridge-daemon subscription template.

5. Expected Artifacts

Modified ai/graph/identityRoots.mjs containing the new agent block.

tobiu referenced in commit 5bfba8e - "feat(graph): add Codex agent identity root (#10478) (#10479) on Apr 28, 2026, 10:50 PM

tobiu closed this issue on Apr 28, 2026, 10:50 PM