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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright #7289
author	kart-u
state	Closed
createdAt	Oct 4, 2025, 11:58 AM
updatedAt	Oct 4, 2025, 12:30 PM
closedAt	Oct 4, 2025, 12:28 PM
mergedAt
branches	`dev` ← `Provider-config-seista-playwright`
url	https://github.com/neomjs/neo/pull/7350

Closed

kart-u commented on Oct 4, 2025, 11:58 AM

Closes #7289

Please make sure to read the Contributing Guidelines:

https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md

What kind of change does this PR introduce? (check at least one)

Bugfix
Feature
Code style update
Refactor
Build-related changes
Other, please describe:

Does this PR introduce a breaking change? (check one)

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

It's submitted to the dev branch, not the main branch
When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information: ✅ Create a new test file at test/playwright/unit/state/ProviderNestedDataConfigs.spec.mjs ✅ Translated all Siesta assertions (t.is) to Playwright expect syntax ✅ All tests pass successfully with npm test ✅ Generated using follow the instructions inside @AGENTS.md protocol

kart-u commented on Oct 4, 2025, 12:30 PM

closed due to mismatch in workflow will open new one