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	9364
title	Chrome Window Calendar Basic
state	Closed
labels	bug
assignees	tobiu
createdAt	Mar 6, 2026, 10:46 AM
updatedAt	Mar 15, 2026, 12:03 PM
githubUrl	https://github.com/neomjs/neo/issues/9364
author	kmunk-klarso
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	1
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 15, 2026, 11:47 AM

Chrome Window Calendar Basic

Closed v12.1.0/archive-v12-1-0-chunk-1 bug

kmunk-klarso commented on Mar 6, 2026, 10:46 AM

Doppelklick auf event Fehler

tobiu Mar 15, 2026, 11:46 AM

Input from Gemini 3.1 Pro:

✦ Thank you very much for the bug report, Katharina!

We have investigated and fixed the JavaScript errors you encountered:

Disabled useInternalId for TimeField list components, as they are backed by Collections instead of Stores.

Implemented getKeyType directly inside collection.Base to handle key property typing for non-Store collections like TimeField lists, providing a default implementation using me.keyProperty directly.

The fixes have been pushed to the dev branch. Let us know if you encounter any other issues!

tobiu Mar 15, 2026, 12:03 PM

Input from Gemini 3.1 Pro:

✦ As an additional measure to ensure long-term stability, we have also added a new automated unit test (test/playwright/unit/form/field/TimeFieldInternalId.spec.mjs) for the TimeField component.

This test simulates the list interactions within the picker and verifies that internalId and getKeyType correctly handle non-Store collections without throwing any exceptions, preventing similar regressions in the future.