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	9850
title	Blog Post: Off the Main Thread — A 2026 Status Report
state	Open
labels	documentationBlog Postai
assignees	[]
createdAt	Apr 10, 2026, 10:34 AM
updatedAt	Apr 10, 2026, 10:34 AM
githubUrl	https://github.com/neomjs/neo/issues/9850
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]

Blog Post: Off the Main Thread — A 2026 Status Report

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

OpendocumentationBlog Postai

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

Summary

Write and publish a blog post providing a 2026 retrospective on the Off-Main-Thread (OMT) architecture thesis, demonstrating that Neo.mjs's 2019 bet has been validated and explaining what comes next.

A2A Context (Fat Ticket Protocol)

Agent: Claude Opus 4.6 (Antigravity) Session Origin: Multi-Window Agent Shell architecture session

Why This Post

The biggest visibility gap for Neo.mjs is the fundamental "what is it?" question. Most developers have never heard of Neo.mjs despite its GA since November 2019 and 30k+ contributions. This post addresses that gap directly by explaining the core architectural thesis and its 7-year validation arc.

Content Outline

The Thesis (2019): Neo.mjs bet that the main thread should only handle DOM manipulation. Everything else — application logic, state management, data processing — runs in Web Workers.
The Validation (2026):
- SharedWorkers now ship in ALL browsers (Safari joined in 2022)
- OffscreenCanvas is stable across all major engines
- Industry momentum: Partytown, worker-based bundlers, Edge Workers
- Open Source Awards 2021: Top-5 "Most Exciting Use of Technology"
The Numbers: Performance benchmarks
- Neo.mjs OMT vs. main-thread frameworks
- VDOM delta update throughput (20k+ updates/second)
- Grid rendering with 100k+ rows (buffered rendering pipeline)
The Multi-Window Proof:
- Only OMT architectures can natively support multi-window apps with shared state
- SharedWorker = shared application heap across browser windows
- Component Teleportation (moving components between windows without destruction)
What's Next (2026+):
- SSG+ vnode content takeover (SEO without sacrificing SPA architecture)
- Neural Link (AI-native runtime introspection)
- Agent OS (autonomous self-improving framework)
- The Klarso migration: enterprise-grade QT→Web proof of concept

Distribution Strategy

Same as Neural Link blog post:

Markdown in learn/blog/ (SSG+ indexable)
Cross-post to dev.to
Hacker News submission
LinkedIn/X with diagrams

Blog Infrastructure

File: learn/blog/off-main-thread-2026-status.md
Update: apps/portal/resources/data/blog.json

Acceptance Criteria

Blog post written in markdown with performance benchmarks and diagrams
Added to blog.json portal index
SSG+ route verified on neomjs.com
Cross-posted to dev.to
Contains working demo links and benchmark reproductions

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

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

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