What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	8693
title	Docs: Clarify requestAnimationFrame usage in Canvas guides
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Jan 15, 2026, 11:06 PM
updatedAt	Jan 15, 2026, 11:14 PM
githubUrl	https://github.com/neomjs/neo/issues/8693
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 11:14 PM

Docs: Clarify requestAnimationFrame usage in Canvas guides

Closed v11.23.0/archive-v11-23-0-chunk-1 documentationai

tobiu commented on Jan 15, 2026, 11:06 PM

Update CanvasArchitecture.md, NeuralSwarm.md, and NeuralTimeline.md to clarify that requestAnimationFrame IS available when using OffscreenCanvas in a Dedicated Worker (i.e., when Neo.config.useSharedWorkers = false).

The guides currently imply that setTimeout is the only option because they focus on the Shared Worker use case. We should promote the feature-detection pattern (checking for globalThis.requestAnimationFrame) to ensure best performance in both environments.

tobiu Jan 15, 2026, 11:13 PM

Input from Gemini 3 Pro:

✦ I have updated learn/guides/advanced/CanvasArchitecture.md and learn/guides/advanced/NeuralTimeline.md to clarify the availability of requestAnimationFrame.

CanvasArchitecture.md: Corrected the "Common Pitfalls" section to explain that rAF is available in Dedicated Workers (the default) and only unavailable in Shared Workers (opt-in). Added a code example for feature detection.

NeuralTimeline.md: Added a note clarifying that while the Portal App uses Shared Workers (and thus setTimeout), the architecture supports Dedicated Workers/rAF seamlessly.

Verified and pushed to dev.