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	8281
title	[Neural Link] Feature: Tool get_computed_styles
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 1, 2026, 8:17 PM
updatedAt	Jan 1, 2026, 8:34 PM
githubUrl	https://github.com/neomjs/neo/issues/8281
author	tobiu
commentsCount	1
parentIssue	8169
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 1, 2026, 8:34 PM

[Neural Link] Feature: Tool get_computed_styles

Closed v11.18.0/archive-v11-18-0-chunk-2 enhancementai

tobiu commented on Jan 1, 2026, 8:17 PM

Implement get_computed_styles to allow AI agents to inspect the actual rendered CSS values of a component.

Requirements:

Main Thread (src/main/DomAccess.mjs):
- Implement getComputedStyle({ id, style }) (or similar signature).
- Support requesting specific style properties or arrays of properties (e.g., ['color', '--button-bg']).
- Expose via remote: { app: [...] }.
Client Service (src/ai/client/ComponentService.mjs):
- Implement getComputedStyles({ componentId, variables }).
- Resolve componentId to a DOM ID.
- Call the remote Neo.main.DomAccess.getComputedStyle.

Why: To verify visual state and theming (The "Visual Gap"). Since getComputedStyle lives in the Main Thread, the App Worker (and the AI) are blind to the actual rendered colors, especially with CSS variables and theme switching.

tobiu Jan 1, 2026, 8:33 PM

Input from Gemini:

✦ Implemented full round-trip for get_computed_styles:

Main Thread: Added getComputedStyle to src/main/DomAccess.mjs (using window.getComputedStyle).

App Worker: Added getComputedStyles to src/ai/client/ComponentService.mjs.

MCP Server:

Updated ai/mcp/server/neural-link/services/ComponentService.mjs to expose the method.

Updated ai/mcp/server/neural-link/services/toolService.mjs mapping.

Updated openapi.yaml with the new tool definition.