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	8362
title	Refactor Portal 'Blog' to 'News' with Left-Tab Architecture for Releases & Posts
state	Closed
labels	documentationepic
assignees	tobiu
createdAt	Jan 6, 2026, 3:50 PM
updatedAt	Jan 8, 2026, 11:51 PM
githubUrl	https://github.com/neomjs/neo/issues/8362
author	tobiu
commentsCount	0
parentIssue	null
subIssues	8386 Refactor Portal Blog to News Section with Tabbed Interface 8388 Refactor Portal Learning Views to Shared Content Viewer 8389 Implement Releases Section using Shared Content View 8390 Implement Tree-Structured Release Index and Portal Integration 8395 Enhance Markdown parser to enforce newlines after headlines 8396 Enhance Markdown parser to support implicit readonly code blocks 8397 Add support for automatic GitHub issue linking in Markdown component 8399 Fix Deep Linking Routing in News TabContainer 8400 Fix Markdown code block trimming destroying indentation 8401 Refine Markdown inline code styling in light theme 8402 Enhance Release tree titles with dates 8403 Pass record instance to Model field convert method 8404 Add styling for Markdown hr tags 8405 Reduce sidebar width for Release view 8411 Fix Release navigation button titles showing HTML and Date 8413 Refactor Portal View Structure: Move Blog and Release under News 8439 Update SEO Service for Nested Routes and News Section 8440 Fix Mobile Layout Overlay in Portal News TabContainer
subIssuesCompleted	18
subIssuesTotal	18
blockedBy	[]
blocking	[]
closedAt	Jan 8, 2026, 11:51 PM

Refactor Portal 'Blog' to 'News' with Left-Tab Architecture for Releases & Posts

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

Closed v11.19.0 documentationepic

tobiu commented on Jan 6, 2026, 3:50 PM

Refactor the Portal's "Blog" section into a comprehensive "News" (or "Updates") center to prepare for SEO indexing and better content discovery.

Objectives:

Rename & Rebrand:
- Rename the top-level "Blog" section to "News" (or similar).
- Update routing and navigation (HeaderToolbar, Viewport) to reflect this change.
Architectural Change (Tabbed Layout):
- Replace the current single-view blog/Container.mjs with a Neo.tab.Container configured with tabBarPosition: 'left' (similar to examples/TabContainer.mjs).
- This allows for multiple content categories.
Content Tabs:
- Tab 1: Blog
  - Preserve the existing Blog functionality (Search + List).
  - Refactor the current blog/Container.mjs to be an item within the new TabContainer.
- Tab 2: Release Notes
  - Create a new view to display Release Notes.
  - Implement a data store (apps/portal/store/Releases.mjs) to fetch release metadata (likely from a JSON index, similar to blog.json).
  - Render release notes (potentially parsing the Markdown files from .github/RELEASE_NOTES/ or using a pre-generated JSON summary).

Strategic Value: This structure prepares the Portal for the upcoming Middleware deployment (SSR/SSG+), ensuring that high-value content like Release Notes is accessible, indexable, and organized alongside Blog posts.

tobiu added the documentation label on Jan 6, 2026, 3:50 PM

tobiu added the enhancement label on Jan 6, 2026, 3:50 PM

tobiu assigned to @tobiu on Jan 6, 2026, 3:51 PM

tobiu removed the enhancement label on Jan 7, 2026, 3:39 PM

tobiu added the epic label on Jan 7, 2026, 3:39 PM

tobiu cross-referenced by #8386 on Jan 7, 2026, 3:49 PM

tobiu added sub-issue #8386 on Jan 7, 2026, 3:53 PM

tobiu added sub-issue #8388 on Jan 7, 2026, 4:49 PM

tobiu added sub-issue #8389 on Jan 7, 2026, 4:59 PM

tobiu added sub-issue #8390 on Jan 7, 2026, 7:11 PM

tobiu added sub-issue #8395 on Jan 7, 2026, 9:32 PM

tobiu added sub-issue #8396 on Jan 7, 2026, 9:46 PM

tobiu added sub-issue #8397 on Jan 7, 2026, 10:06 PM

tobiu added sub-issue #8399 on Jan 7, 2026, 11:28 PM

tobiu added sub-issue #8400 on Jan 8, 2026, 12:12 AM

tobiu added sub-issue #8401 on Jan 8, 2026, 12:35 AM

tobiu added sub-issue #8402 on Jan 8, 2026, 1:06 AM

tobiu added sub-issue #8403 on Jan 8, 2026, 1:06 AM

tobiu added sub-issue #8404 on Jan 8, 2026, 1:11 AM

tobiu added sub-issue #8405 on Jan 8, 2026, 1:29 AM

tobiu added sub-issue #8411 on Jan 8, 2026, 10:13 AM

tobiu added sub-issue #8413 on Jan 8, 2026, 10:40 AM

tobiu added sub-issue #8439 on Jan 8, 2026, 8:48 PM

tobiu added sub-issue #8440 on Jan 8, 2026, 9:23 PM

tobiu closed this issue on Jan 8, 2026, 11:51 PM