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	8957
title	Fix: Sparkline Pulse Artifact Persistence
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 3, 2026, 11:24 AM
updatedAt	Feb 3, 2026, 11:32 AM
githubUrl	https://github.com/neomjs/neo/issues/8957
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 3, 2026, 11:32 AM

Fix: Sparkline Pulse Artifact Persistence

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

Closed v12.0.0 bugai

tobiu commented on Feb 3, 2026, 11:24 AM

The pulse animation in Neo.canvas.Sparkline leaves a visual artifact at the end of the chart when the animation completes.

Symptoms:

The pulse "walks" the entire x-dimension as expected.
Once the animation ends (progress >= 1), the visual representation of the pulse stays at the last position instead of being removed.
It remains until the next animation cycle starts.

Expected Behavior:

The pulse should be completely removed from the canvas once the animation finishes.

Context:

This affects the Neo.canvas.Sparkline component.
The renderLoop cleanup logic or the final draw call seems to be ineffective in clearing the last frame.

tobiu added the bug label on Feb 3, 2026, 11:24 AM

tobiu added the ai label on Feb 3, 2026, 11:24 AM

tobiu added parent issue #8930 on Feb 3, 2026, 11:24 AM

tobiu referenced in commit 7e251c3 - "Fix: Sparkline Pulse Artifact Persistence (#8957)" on Feb 3, 2026, 11:31 AM

tobiu Feb 3, 2026, 11:31 AM

Input from Gemini 3 Pro:

✦ I have applied a follow-up fix based on your feedback.

Root Cause: The "artifact" in the initial state was likely the static "End Point" marker, which was:

Being clipped at the edge of the canvas (radius > 0 at x=width), looking like a glitch.

Perceived as a "resting pulse" because it resembled the pulse core.

Changes:

Padding: Added paddingX = 4 and increased paddingY to 6. This ensures that markers, line strokes, and pulse effects (glow radius 6) are no longer clipped at the edges.

Removal: Removed the static "End Point" marker entirely. Now, when the chart is idle or the animation finishes, only the clean sparkline curve is visible. This directly addresses the "it should get removed" requirement.

The result is a cleaner chart with no clipped elements and no lingering artifacts after the pulse animation.

tobiu assigned to @tobiu on Feb 3, 2026, 11:32 AM

tobiu closed this issue on Feb 3, 2026, 11:32 AM