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	8545
title	Enhancement: "Chameleon Pulse" & Render Loop Polish
state	Closed
labels	enhancementdesignai
assignees	tobiu
createdAt	Jan 11, 2026, 2:59 PM
updatedAt	Jan 11, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/8545
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 11, 2026, 3:18 PM

Enhancement: "Chameleon Pulse" & Render Loop Polish

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

Closed v11.20.0 enhancementdesignai

tobiu commented on Jan 11, 2026, 2:59 PM

Goal: Elevate the timeline animation from visual decoration to semantic data visualization.
Concept (Chameleon Pulse): The pulse should react to the content it passes.
- Default: Neo Blue (rgba(64, 196, 255, 1)).
- Interaction: When approaching/orbiting a node with a specific status color (e.g., Closed=Purple, Reopened=Green), the pulse should smoothly transition to that color.
Technical Polish:
- Replace setTimeout(..., 1000/60) with requestAnimationFrame for optimal V-Sync and battery efficiency.
- Inject node-specific colors (based on icon class or raw record data) into the nodes array sent to the worker.
- Interpolate the ctx.strokeStyle gradient based on proximity.

tobiu added the enhancement label on Jan 11, 2026, 2:59 PM

tobiu added the design label on Jan 11, 2026, 2:59 PM

tobiu added the ai label on Jan 11, 2026, 2:59 PM

tobiu referenced in commit 98665fb - "feat: Implement 'Chameleon Pulse' animation with data-driven colors (#8545)" on Jan 11, 2026, 3:17 PM

tobiu Jan 11, 2026, 3:17 PM

Input from Gemini 3 Pro:

✦ Implemented the "Chameleon Pulse" effect with robust data handling.

The Problem

The animation was stuck on "Blue" because the sections store (driven by ContentSection model) was stripping out the color property from the timeline data.

The Solution

Data Model: Updated Portal.model.ContentSection.mjs to include the color field.

Data Logic: Updated Component.mjs to resolve semantic colors:

Labels: Looked up from the labels store (e.g., bug -> Red).

State: Mapped locally (Closed -> Purple, Reopened -> Green).

Visuals: Updated TicketCanvas.mjs (Worker):

Receives the Hex color.

Converts Hex to RGB.

Interpolates the pulse color from Base Blue to Node Color based on proximity (<100px).

Uses setTimeout (1000/60) for compatibility with SharedWorkers (no rAF).

The pulse now dynamically changes color as it flows through different event types, providing immediate visual feedback on the ticket's history.

tobiu assigned to @tobiu on Jan 11, 2026, 3:17 PM

tobiu closed this issue on Jan 11, 2026, 3:18 PM