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	9919
title	feat: Implement fs.watch Daemonization for Autonomous Orchestrator
state	Closed
labels	enhancementai
assignees	[]
createdAt	Apr 12, 2026, 3:23 PM
updatedAt	May 28, 2026, 3:52 AM
githubUrl	https://github.com/neomjs/neo/issues/9919
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 28, 2026, 3:52 AM

feat: Implement fs.watch Daemonization for Autonomous Orchestrator

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

tobiu commented on Apr 12, 2026, 3:23 PM

Description

Currently, the Neo.ai.agent.Orchestrator runs as a single-turn execution, parsing sandman_handoff.md and triggering the Swarm. To achieve true continuous automation, the Orchestrator needs to run as a persistent daemon.

Architectural Rationale

We need to attach an fs.watch listener (or equivalent polling structure) to the sandman_handoff.md manifest safely.
When DreamService generates a new handoff file overnight, the Orchestrator should seamlessly boot up the agent cluster, inject the system:golden-path events, and go back to sleep.
Agent Context: This allows the Swarm to trigger asynchronously decoupling the orchestration cycle completely from manual CLI execution.

Origin Session ID: 95bf4a2b-d84e-4f70-945b-f558ba924d3a

tobiu added the enhancement label on Apr 12, 2026, 3:23 PM

tobiu added the ai label on Apr 12, 2026, 3:23 PM