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	8617
title	Refactor StringBasedRenderer for API Parity (Separate Creation from Insertion)
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Jan 13, 2026, 8:53 PM
updatedAt	Jan 14, 2026, 12:11 AM
githubUrl	https://github.com/neomjs/neo/issues/8617
author	tobiu
commentsCount	1
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 14, 2026, 12:10 AM

Refactor StringBasedRenderer for API Parity (Separate Creation from Insertion)

Closed v11.21.0/archive-v11-21-0-chunk-1 airefactoringcore

tobiu commented on Jan 13, 2026, 8:53 PM

During Fragment implementation, it was noted that StringBasedRenderer.insertNodeAsString handles both creation (from string) and insertion (into parent), whereas DomApiRenderer.createDomTree returns the node for the caller to insert. This inconsistency forced DeltaUpdates to bypass insertNodeAsString and use htmlStringToElement directly for Fragments.

Goal: Refactor StringBasedRenderer to expose a createNode (or similar) method that returns a DocumentFragment/Element from the delta, and update DeltaUpdates to handle the insertion step uniformly for both renderers. This improves code reuse and maintainability.

tobiu Jan 14, 2026, 12:11 AM

Input from Gemini 3 Pro:

✦ Refactored StringBasedRenderer to expose createNode({outerHTML}), aligning it with the DomApiRenderer creation pattern.

Critical Fixes & verification:

Unified Insertion: DeltaUpdates.insertNode now uses a consistent creation-then-insertion flow for both renderers.

Scroll State Preservation: Fixed a bug where DomApiRenderer lost scroll state during insertion. Implemented a unified postMountUpdates handler that supports both node-reference (DomApi) and ID-lookup (StringBased) formats.

Refactoring: Removed unused insertNodeAsString and htmlStringToElement, consolidating logic into createNode.

Testing: Added regression tests in FragmentDeltaUpdates.spec.mjs verifying scrollTop preservation for both DomApiRenderer and StringBasedRenderer.