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	8535
title	Implement Timeline Navigation in Sections List for Tickets
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 11, 2026, 2:29 AM
updatedAt	Jan 11, 2026, 2:58 AM
githubUrl	https://github.com/neomjs/neo/issues/8535
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 11, 2026, 2:58 AM

Implement Timeline Navigation in Sections List for Tickets

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

Closed v11.20.0 enhancementai

tobiu commented on Jan 11, 2026, 2:29 AM

In the Portal App's Ticket view, the right-side "Sections List" currently parses markdown headers (H2/H3), which is not useful for the timeline-based ticket view. We need to refactor Portal.view.news.tickets.Component to populate the Sections List with timeline items (Body, Comments, Events) instead.

Update modifyMarkdown to collect timeline items.
Update renderTimeline to inject data-record-id anchors and metadata.
Ensure the "Description" (ticket body) is the first item.
Update the sections store with the new timeline data.

tobiu added the enhancement label on Jan 11, 2026, 2:29 AM

tobiu added the ai label on Jan 11, 2026, 2:29 AM

tobiu referenced in commit 71ad416 - "feat: Implement timeline navigation in Sections List (#8535)" on Jan 11, 2026, 2:57 AM

tobiu Jan 11, 2026, 2:57 AM

Input from Gemini 3 Pro:

✦ I have successfully implemented the timeline navigation in the Sections List for the Ticket view.

Summary of Changes:

Model Update: Updated Portal.model.ContentSection to include icon and image fields and changed id to String type to support timeline IDs (e.g., "timeline-0").

Controller Update: Refactored Portal.view.news.tickets.MainContainerController.onIntersect to handle string-based record IDs, fixing synchronization between scrolling and the list selection.

View Updates:

Component.mjs:

Restored missing private fields (#dateTimeFormatHistory, #dateTimeFormatToday).

Updated modifyMarkdown to initialize timelineData with the ticket body ("Description").

Updated renderTimeline to populate timelineData with comments and events, using specific IDs, icons, and labels (e.g., "Bug (User)" instead of "Label").

Injected data-record-id attributes into the generated HTML for scroll anchoring.

Updated the sections store with the fully populated timelineData.

SectionsList.mjs: Updated createItemContent to render icons (font-awesome) and images (avatars) alongside text.

Styling: Updated SectionsList.scss to style the new avatars and icons, ensuring correct vertical alignment with the text.

Outcome: The right-side "Sections List" now dynamically reflects the structure of the ticket timeline (Description, Comments, Events), providing a much more useful navigation tool than the previous generic header list. Clicking items correctly scrolls to the content, and scrolling updates the list selection.

tobiu closed this issue on Jan 11, 2026, 2:58 AM

tobiu assigned to @tobiu on Jan 11, 2026, 2:58 AM