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	9950
title	Epic: Abstracting the Operating Environment (Agent OS v3)
state	Open
labels	epicaiarchitecture
assignees	[]
createdAt	Apr 13, 2026, 11:28 AM
updatedAt	Jun 5, 2026, 7:17 PM
githubUrl	https://github.com/neomjs/neo/issues/9950
author	tobiu
commentsCount	1
parentIssue	null
subIssues	9951 Scaffold signal_state_transition MCP Endpoint 9952 Sandman Handoff: Top 5 Actionable Tasks Dashboarding 9953 MCP Progressive Disclosure Endpoint 9957 Scaffold pull-request Progressive Disclosure Skill 9958 System Prompt Token Optimization via Mermaid Graphs 10018 Autonomous Healthcheck Workflow for Frontier Model Agents
subIssuesCompleted	6
subIssuesTotal	6
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 9951 Scaffold signal_state_transition MCP Endpoint
blocking	[]

Epic: Abstracting the Operating Environment (Agent OS v3)

Open Backlog/active-chunk-1 epicaiarchitecture

tobiu commented on Apr 13, 2026, 11:28 AM

Goal

Provide a native, secure operating environment wrapper for Swarm Agents that abstracts Orchestrator tracking and MCP Schema routing into high-level tools. This Epic prevents prompt-bloat ("Catastrophic Context Collapse") by reducing unstructured state transitions.

Implementation Paradigm

Instead of treating LLM agents like human Terminal Operators by waiting for conversational "I am done" strings, we provide robust state signaling endpoints (e.g., signal_state_transition) allowing the Node.js OS to securely trap the repository state while allowing the Frontier models to retain raw Git CLI access.

Sub-Issues

Scaffold signal_state_transition MCP Endpoint
Purge Git Mandates & Optimize Dashboard
MCP Progressive Disclosure Endpoint

tobiu added the epic label on Apr 13, 2026, 11:28 AM

tobiu added the ai label on Apr 13, 2026, 11:28 AM

tobiu added the architecture label on Apr 13, 2026, 11:28 AM

tobiu added sub-issue #9951 on Apr 13, 2026, 11:28 AM

tobiu added sub-issue #9952 on Apr 13, 2026, 11:28 AM

tobiu added sub-issue #9953 on Apr 13, 2026, 11:28 AM

tobiu added sub-issue #9957 on Apr 13, 2026, 11:34 AM

tobiu added sub-issue #9958 on Apr 13, 2026, 11:39 AM

tobiu marked this issue as being blocked by #9951 on Apr 13, 2026, 1:13 PM

tobiu cross-referenced by PR #9968 on Apr 13, 2026, 2:49 PM

tobiu added sub-issue #10018 on Apr 14, 2026, 8:57 PM