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	8396
title	Enhance Markdown parser to support implicit readonly code blocks
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 7, 2026, 9:46 PM
updatedAt	Jan 7, 2026, 9:55 PM
githubUrl	https://github.com/neomjs/neo/issues/8396
author	tobiu
commentsCount	1
parentIssue	8362
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 7, 2026, 9:55 PM

Enhance Markdown parser to support implicit readonly code blocks

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

Closed v11.19.0 enhancementai

tobiu commented on Jan 7, 2026, 9:46 PM

Update Neo.component.Markdown to treat all code blocks as readonly by default, removing the requirement for the explicit readonly flag.

Parsing Order: live-preview, neo-component, and mermaid blocks are already parsed first and replaced with placeholders.
Generic Fallback: The parser will then match any remaining triple-backtick code blocks.
Implicit Readonly: These blocks will be processed as readonly code blocks with syntax highlighting.
Default Language: If no language is specified (e.g. just ```), it will default to plaintext.

This simplifies writing markdown for the portal and release notes.

tobiu added the enhancement label on Jan 7, 2026, 9:46 PM

tobiu added the ai label on Jan 7, 2026, 9:46 PM

tobiu added parent issue #8362 on Jan 7, 2026, 9:46 PM

tobiu assigned to @tobiu on Jan 7, 2026, 9:46 PM

tobiu referenced in commit 2b1416f - "enhancement: Enhance Markdown parser to support implicit readonly code blocks (#8396)" on Jan 7, 2026, 9:54 PM

tobiu Jan 7, 2026, 9:54 PM

Input from Gemini 3 Pro:

✦ I have enhanced Neo.component.Markdown to support implicit readonly code blocks.

Changes:

Generic Regex: Replaced the restricted regexReadonly with a generic regexCodeBlock that matches any triple-backtick block.

Implicit Readonly: All code blocks are now processed as readonly blocks by default (after live-preview and other special blocks are extracted).

Smart Defaults: If a language is not specified (e.g. ```) or is text, it defaults to plaintext.

Robust Error Handling: The parser now catches errors from HighlightJS (e.g., if an unknown language is specified like ```java) and automatically falls back to plaintext highlighting, preventing parser crashes.

This simplifies writing markdown for the Portal and Release Notes, as readonly flags are no longer required.

tobiu closed this issue on Jan 7, 2026, 9:55 PM

tobiu referenced in commit 31cc663 - "feat: Enhance Markdown parser (implicit readonly, ticket linking) (#8396, #8397)" on Jan 7, 2026, 11:11 PM