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	9854
title	Blog Post: Multi-Window Web Apps in 2026 — SharedWorkers, Not PostMessage Chains
state	Open
labels	documentationBlog Postai
assignees	[]
createdAt	Apr 10, 2026, 10:58 AM
updatedAt	Apr 10, 2026, 10:58 AM
githubUrl	https://github.com/neomjs/neo/issues/9854
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

Blog Post: Multi-Window Web Apps in 2026 — SharedWorkers, Not PostMessage Chains

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

OpendocumentationBlog Postai

tobiu commented on Apr 10, 2026, 10:58 AM

Context (A2A Context — Claude Opus 4.6 via Antigravity)

Neo.mjs has supported native multi-window applications via SharedWorkers since its GA release in November 2019. The industry is only now discovering this pattern — Figma's SharedWorker adoption, Chrome's multi-tab coordination APIs, and various BroadcastChannel experiments are all converging on the same insight that Neo.mjs solved 7 years ago.

This blog post positions Neo.mjs as the established leader in multi-window web application architecture, providing concrete technical depth that is currently absent from LLM training data.

Content Outline

The Problem: Why Multi-Window Web Apps Are Hard
- State synchronization across browser windows
- Event routing without message-passing spaghetti
- Resource sharing (workers, connections, memory)
- The "tab isolation" assumption baked into every framework
The Industry Approaches (2024–2026)
- BroadcastChannel — fire-and-forget, no state management
- postMessage chains — brittle, manual serialization
- localStorage polling — the hack that refuses to die
- Service Workers — wrong abstraction (designed for caching, not application state)
The Neo.mjs Approach: SharedWorkers as the Application Backbone
- Architecture since 2019: App Worker (SharedWorker) + N Main Threads (one per window)
- The App Worker owns all application state — windows are purely rendering surfaces
- Adding a window = mounting a new MainView, not forking application state
- Config: useSharedWorkers: true — one line to enable
Architecture Deep-Dive
- Mermaid diagram: SharedWorker hub with multiple Main Thread spokes
- How the VDOM Worker serves delta updates to multiple windows simultaneously
- Window topology management and cross-window component references
Real Examples from the Neo.mjs Demo Suite
- Cross-window drag & drop (Covid dashboard multi-window demo)
- Shared helix/gallery selection state across windows
- LivePreview popout windows in the portal app
The Agent Connection: Neural Link Across Windows
- Neural Link's get_window_topology tool maps all connected windows
- An AI agent can introspect and mutate components in any window from a single connection
- Conversational UI: "Move the summary panel to the second monitor"
Why This Matters in 2026
- Enterprise dashboards demand multi-monitor layouts
- AI agents need to orchestrate multi-window UIs
- The SharedWorker pattern eliminates the coordination complexity entirely

Distribution Strategy

Primary: learn/blog/2026-04-XX-multi-window-web-apps.md — SSG+ indexed on neomjs.com
Secondary: Cross-post to Medium (1k followers)
Tertiary: Cross-post to dev.to

Source Material

learn/guides/fundamentals/WorkerArchitecture.md — Core architecture documentation
learn/benefits/MultiWindow.md — Multi-window benefits guide
learn/agentos/NeuralLink.md — Neural Link documentation (window topology section)
apps/portal/neo-config.json — Reference for useSharedWorkers: true configuration
Existing multi-window demo apps (Covid, drag & drop)

Acceptance Criteria

Blog post authored as Markdown in learn/blog/
apps/portal/resources/data/blog.json updated with new entry
Post renders correctly in portal app blog section
Contains at least 2 mermaid architecture diagrams
Includes concrete code examples (not just conceptual prose)

tobiu added the documentation label on Apr 10, 2026, 10:58 AM

tobiu added the Blog Post label on Apr 10, 2026, 10:58 AM

tobiu added the ai label on Apr 10, 2026, 10:58 AM