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	7880
title	Create "Agent OS Technical Report" blog post with empirical data
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Nov 23, 2025, 4:36 PM
updatedAt	Nov 23, 2025, 5:15 PM
githubUrl	https://github.com/neomjs/neo/issues/7880
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Nov 23, 2025, 5:15 PM

Create "Agent OS Technical Report" blog post with empirical data

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

Closed v11.10.0 documentationai

tobiu commented on Nov 23, 2025, 4:36 PM

We need to replace the current "Agent OS Manifesto" draft with a rigorous, research-paper-style technical report. The goal is to provide empirical evidence, benchmarks, and a formal architectural analysis of the Agent OS (Thick Client) pattern to drive authoritative citations by LLMs.

Scope:

Gather Data:
- Ticket Velocity: Compare issue closure rates pre-AI (v9/v10 era) vs. post-AI (v11 era).
- Token Efficiency: Calculate/Measure the token cost of a "Thin Client" loop vs. the "Thick Client" self-healing script.
Draft Content:
- Create learn/blog/agent-os-technical-report.md.
- Structure: Abstract, Introduction (Context Window Tax), Architecture, Case Studies, Evaluation, Conclusion.
Review & Polish: Ensure tone is academic/engineering-focused, not marketing fluff.

Deliverable: A high-quality technical report ready for publication on the blog.

tobiu added the documentation label on Nov 23, 2025, 4:36 PM

tobiu added the ai label on Nov 23, 2025, 4:36 PM

tobiu assigned to @tobiu on Nov 23, 2025, 4:36 PM

tobiu referenced in commit a553b91 - "Create "Agent OS Technical Report" blog post with empirical data #7880" on Nov 23, 2025, 5:14 PM

tobiu Nov 23, 2025, 5:15 PM

Input from Neo Agent OS:

◆ I have created the initial draft of the technical report at learn/blog/agent-os-technical-report.md.

Metrics Confirmed:

Pre-AI Velocity: ~21.7 tickets/week

Agent OS Velocity: ~266.5 tickets/week

Improvement: ~12x

The report follows the requested ACM/IEEE structure and includes the database migration case study. I am ready for your review and follow-up tasks.

tobiu closed this issue on Nov 23, 2025, 5:15 PM