What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	8661
title	Epic: Home Hero Canvas (The Neural Swarm)
state	Closed
labels	enhancementepicai
assignees	tobiu
createdAt	Jan 15, 2026, 2:05 AM
updatedAt	Jan 15, 2026, 12:37 PM
githubUrl	https://github.com/neomjs/neo/issues/8661
author	tobiu
commentsCount	0
parentIssue	null
subIssues	8662 Scaffold Home Canvas Architecture 8663 Implement Neural Network Physics & Rendering 8664 Implement Home Canvas Interaction & Parallax 8665 Refactor HomeCanvas Styling & Pointer Events 8666 Optimize HomeCanvas Lifecycle (Pause/Resume) 8667 Optimize HomeCanvas Rendering (Gradient Caching) 8668 Implement Cluster Physics & Mutable Topology 8669 Implement Autonomous Agent Drones (Boids) 8670 Implement Data Flow & Interaction Visuals 8671 Implement Topology Mutation (Re-parenting) 8672 Implement Cluster Drift (Flow Fields) 8673 Implement Elastic Connections & Breathing 8674 Implement Agent-Driven State 8675 Implement Interactive Physics (Drag/Throw) 8676 Fix Cluster Drift Bias & Boundaries 8677 Enhance Shockwave Visuals 8678 Implement Hero Container Wrapper 8679 Enhance Neural Swarm Documentation 8680 Write Guide: The Neural Swarm 8681 Restore Shockwave Physics Interaction 8682 Optimize Neural Swarm Contrast for Light Theme 8683 Home Hero Canvas: Visual Polish (Blue Shockwave) & GC Optimization
subIssuesCompleted	22
subIssuesTotal	22
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 12:37 PM

Epic: Home Hero Canvas (The Neural Swarm)

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.22.0 enhancementepicai

tobiu commented on Jan 15, 2026, 2:05 AM

Objective

Implement a living, "Agent-Native" simulation for the Portal Home Hero section. Instead of a passive network background, this canvas will visualize the Neo.mjs Application Engine as a mutable, multi-threaded runtime inhabited by AI agents.

Concept: "The Neural Swarm"

A simulated ecosystem representing the "Living Graph" of a Neo.mjs application.

The Nodes: Represent persistent runtime objects (Components).
The Agents: Represent the "Ghost in the Shell" (Neural Link).
The Topology: Mutable, fluid, and reconfigurable (Atomic Moves).

Features

1. Living Topology (Object Permanence)

Cluster Physics: Nodes are not random; they form hierarchical clusters (Components inside Containers).
Mutation: Occasionally, a sub-cluster will detach from its parent, drift, and re-attach to a new cluster, visualizing Atomic Moves (Release v11.21.0).
Initialization: Use Poisson Disk Sampling or Golden Spiral distribution to ensure instant, uniform screen coverage (fixing the "expanding blob" issue).

2. Autonomous Agents (The Neural Link)

Seeker Drones: Fast-moving energy points that behave like autonomous agents (Boids behavior).
Inspection: Agents fly between clusters, "scanning" nodes (triggering a highlight effect) and "repairing" links.
Trails: Agents leave fading data trails, visualizing the high-frequency communication of the SharedWorker architecture.

3. Data Flow & Pulse

Signal Packets: Pulses of light travel along the connections between nodes, visualizing the data flow between Workers.
Deep Parallax: 3-4 layers of depth to create a volumetric feel.

Architecture

App Component: Portal.view.home.HomeCanvas
- Resizing, DOM placement, lifecycle management.
Shared Worker: Portal.canvas.HomeCanvas
- Physics Engine: Custom Verlet integration for stability.
- Boid System: Separation, Alignment, Cohesion for Agents.
- Render Loop: Zero-Allocation implementation using Float32Array buffers for all entities.

Visual Theme

Palette: "Luminous Flux" (#3E63DD, #8BA6FF) with bright white/cyan highlights (#40C4FF) for Agents and Data Packets.
Atmosphere: Deep, premium, desktop-class aesthetic.

tobiu assigned to @tobiu on Jan 15, 2026, 2:05 AM

tobiu added the enhancement label on Jan 15, 2026, 2:05 AM

tobiu added the epic label on Jan 15, 2026, 2:05 AM

tobiu added the ai label on Jan 15, 2026, 2:05 AM

tobiu added sub-issue #8662 on Jan 15, 2026, 2:05 AM

tobiu added sub-issue #8663 on Jan 15, 2026, 2:06 AM

tobiu added sub-issue #8664 on Jan 15, 2026, 2:06 AM

tobiu added sub-issue #8665 on Jan 15, 2026, 2:31 AM

tobiu added sub-issue #8666 on Jan 15, 2026, 2:42 AM

tobiu added sub-issue #8667 on Jan 15, 2026, 2:55 AM

tobiu changed title from Epic: Home Hero Canvas (Neural Connectome) to Epic: Home Hero Canvas (The Neural Swarm) on Jan 15, 2026, 3:10 AM

tobiu added sub-issue #8668 on Jan 15, 2026, 3:12 AM

tobiu added sub-issue #8669 on Jan 15, 2026, 3:13 AM

tobiu added sub-issue #8670 on Jan 15, 2026, 3:13 AM

tobiu added sub-issue #8671 on Jan 15, 2026, 3:39 AM

tobiu added sub-issue #8672 on Jan 15, 2026, 3:39 AM

tobiu added sub-issue #8673 on Jan 15, 2026, 3:39 AM

tobiu added sub-issue #8674 on Jan 15, 2026, 3:39 AM

tobiu added sub-issue #8675 on Jan 15, 2026, 3:39 AM

tobiu added sub-issue #8676 on Jan 15, 2026, 4:29 AM

tobiu added sub-issue #8677 on Jan 15, 2026, 4:29 AM

tobiu added sub-issue #8678 on Jan 15, 2026, 4:29 AM

tobiu added sub-issue #8679 on Jan 15, 2026, 4:29 AM

tobiu added sub-issue #8680 on Jan 15, 2026, 4:29 AM

tobiu added sub-issue #8681 on Jan 15, 2026, 9:59 AM

tobiu added sub-issue #8682 on Jan 15, 2026, 10:13 AM

tobiu added sub-issue #8683 on Jan 15, 2026, 11:56 AM

tobiu closed this issue on Jan 15, 2026, 12:37 PM