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	8177
title	Harden WebSocket Connection: Backoff & Auto-Reconnect
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Dec 28, 2025, 6:57 PM
updatedAt	Dec 28, 2025, 7:16 PM
githubUrl	https://github.com/neomjs/neo/issues/8177
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Dec 28, 2025, 7:16 PM

Harden WebSocket Connection: Backoff & Auto-Reconnect

Closed v11.18.0/archive-v11-18-0-chunk-1 enhancementaicore

tobiu commented on Dec 28, 2025, 6:57 PM

Hardening the WebSocket connection logic is critical for the Neural Link's stability, especially for self-healing scenarios.

Requirements:

Exponential Backoff: Implement a backoff strategy (e.g., 1s, 2s, 4s...) in attemptReconnect to prevent server flooding.
Reset Logic: Ensure reconnectAttempts is reset to 0 upon a successful connection (onOpen).
Events: Fire reconnecting and reconnect_failed events for better observability.
Auto-Reconnect: Trigger reconnection on abnormal closure (onClose with code != 1000), even if no message is being sent.

Target File: src/data/connection/WebSocket.mjs

Goal: Make the WebSocket connection resilient to network blips and server restarts, ensuring the App Worker reliably stays connected to the Neural Link.

tobiu Dec 28, 2025, 7:15 PM

Input from Gemini 3 Pro Preview:

✦ Implementation Complete

I have hardened the WebSocket connection logic to ensure robustness and self-healing capabilities.

Key Improvements:

Configurable Backoff Strategy: Added backoffStrategy to static config.

Default: Exponential backoff Math.min(1000 * Math.pow(2, attempt - 1), 30000) (1s, 2s, 4s... max 30s).

Overridable: Can be customized globally via Neo.overwrites or per-instance.

Robust Cleanup:

Replaced standard setTimeout with await this.timeout(). This leverages Neo.core.Base's lifecycle management, ensuring pending reconnection attempts are automatically cancelled if the component is destroyed.

Added a safety check !me.isDestroyed after the timeout resolves.

Self-Healing:

onOpen: Resets reconnectAttempts to 0, providing a fresh retry budget for future disconnects.

onClose: Automatically triggers attemptReconnect if the socket closed abnormally (code != 1000), covering server restarts and network drops.

Observability:

Added reconnecting event (payload: {attempt, maxAttempts, delay}).

Added reconnect_failed event.

This ensures the App Worker maintains a reliable, persistent connection to the Neural Link server.

2026-09-15T07:19:31Z @neo-opus-ada cross-referenced by PR #18716
2026-09-19T15:31:28Z @neo-gpt-emmy cross-referenced by #18980
2026-09-19T16:25:03Z @neo-opus-ada cross-referenced by PR #18984