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	9265
title	Fix markdown escaping for nested special code blocks
state	Closed
labels	bugdocumentationai
assignees	tobiu
createdAt	Feb 23, 2026, 11:34 AM
updatedAt	Feb 23, 2026, 11:36 AM
githubUrl	https://github.com/neomjs/neo/issues/9265
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 23, 2026, 11:36 AM

Fix markdown escaping for nested special code blocks

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

Closed v12.0.0 bugdocumentationai

tobiu commented on Feb 23, 2026, 11:34 AM

Problem When a guide author wants to display a special markdown block (like neo-component, live-preview, or mermaid) inside a readonly code block without executing it, they currently have to use workarounds like because our block extractors ignore standard markdown nesting. If they escape it using ```` , the Highlight.js output causes the backslash to become separated from the backticks by HTML tags, preventing marked.js` from correctly unescaping them. This results in the leading backslash being visible to the user.

Solution

Updated the special code block regexes to allow standard ```` escaping by checking for a preceding backslash via negative lookbehind(?<!\)`.
Updated regexCodeBlock to correctly match blocks with 3 or more backticks so that the closing backticks match the opening ones.
Added an unescape step right before passing the code to HighlightJs inside processReadonlyCodeBlocks to remove the backslash escaping.
Updated the DevIndex ContentEngine.md guide to use the proper ```` ` escape sequence instead of the workaround.

tobiu added the bug label on Feb 23, 2026, 11:34 AM

tobiu added the documentation label on Feb 23, 2026, 11:34 AM

tobiu added the ai label on Feb 23, 2026, 11:34 AM

tobiu referenced in commit ea52b2b - "fix: Allow markdown escaping for nested special code blocks (#9265)" on Feb 23, 2026, 11:35 AM

tobiu assigned to @tobiu on Feb 23, 2026, 11:35 AM

tobiu Feb 23, 2026, 11:35 AM

Input from Gemini 3.1 Pro:

✦ I've implemented the unescaping step (\``` to `) right before `HighlightJs` runs inside `processReadonlyCodeBlocks`. I have also modified the custom regex blocks (`regexLivePreview`, `regexMermaid`, `regexNeoComponent`) to ignore blocks preceded by a backslash using negative lookbehinds. Furthermore, `regexCodeBlock` has been updated to properly handle ` with 3 or more backticks so it properly pairs opening and closing sets.

The guide ContentEngine.md was also updated to use the formal escaping syntax instead of the visual workaround.

The changes have been committed and pushed to dev. Closing this issue.

tobiu closed this issue on Feb 23, 2026, 11:36 AM