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	8689
title	Enhance Timeline Item Labels for Sub-Issues
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 15, 2026, 1:51 PM
updatedAt	Jan 15, 2026, 1:57 PM
githubUrl	https://github.com/neomjs/neo/issues/8689
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 1:57 PM

Enhance Timeline Item Labels for Sub-Issues

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

Closed v11.22.0 enhancementai

tobiu commented on Jan 15, 2026, 1:51 PM

Goal: Improve the clarity of timeline items in the Portal Ticket view (apps/portal/view/news/tickets/Component.mjs), specifically for sub-issue events.

Current Behavior: Events like "added sub-issue #123" are currently summarized as "Label (user)" in the timeline navigation (sections store), which is uninformative.

Desired Behavior: When the action involves adding or removing a sub-issue:

Parse the sub-issue ID from the action string.
Format the timeline item name as Added sub-issue #<id> or Removed sub-issue #<id>.
Remove the user attribution from the name for these specific events, as the action itself is more important.

Task:

Update renderTimeline() in apps/portal/view/news/tickets/Component.mjs.
Add specific parsing logic for added sub-issue and removed sub-issue actions.
Ensure the name property pushed to me.timelineData reflects this meaningful summary.

tobiu added the enhancement label on Jan 15, 2026, 1:51 PM

tobiu added the ai label on Jan 15, 2026, 1:51 PM

tobiu referenced in commit 1a257de - "enhancement: Improve timeline labels for sub-issue events (#8689)" on Jan 15, 2026, 1:56 PM

tobiu assigned to @tobiu on Jan 15, 2026, 1:56 PM

tobiu Jan 15, 2026, 1:56 PM

Input from Gemini 3 Pro:

✦ I have enhanced the renderTimeline method in apps/portal/view/news/tickets/Component.mjs.

Changes:

Implemented parsing logic to detect "sub-issue" events in the timeline action string.

Extracted the sub-issue ID using regex.

Formatted the timeline item label as "Added/Removed sub-issue #ID" instead of the generic "Label (user)".

Retained the existing behavior for standard label changes and other events.

This change significantly improves the readability of the timeline navigation for complex tickets with many sub-issues.

tobiu closed this issue on Jan 15, 2026, 1:57 PM