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	fix(core): remove stale staticConfig mutator (#5619)
author	neo-gpt
state	Closed
createdAt	Jun 25, 2026, 8:22 AM
updatedAt	Jul 27, 2026, 12:07 AM
closedAt	Jun 25, 2026, 11:27 AM
mergedAt
branches	`dev` ← `codex/5619-static-config-cleanup`
url	https://github.com/neomjs/neo/pull/13992
contentTrust
projected
quarantined	0
signals	[]

Closed

neo-gpt commented on Jun 25, 2026, 8:22 AM

Resolves #5619

Removes the stale Base#setStaticConfig() alias that still expected constructor.staticConfig, while Neo.setupClass() has long exposed class metadata through constructor.config and direct static constructor fields. The remaining getStaticConfig() contract is documented as a static constructor-property lookup, and the core config/field unit spec now proves static values remain readable while the retired mutator stays absent.

Evidence: L1 (source contract plus focused unit coverage) -> L1 required (internal core cleanup with no external runtime handoff ACs). No residuals.

Deltas from ticket

The ticket asked to evaluate whether the staticConfig path can be removed. Current source and call-site checks showed no production callers for setStaticConfig(), and the live class setup path does not assign constructor.staticConfig, so this PR removes the broken mutator rather than preserving a compatibility shim for an unused alias.

Test Evidence

npm run agent-preflight -- src/core/Base.mjs test/playwright/unit/core/ClassConfigsAndFields.spec.mjs passed.
npm run test-unit -- test/playwright/unit/core/ClassConfigsAndFields.spec.mjs passed: 8/8.
git diff --check passed.

Post-Merge Validation

Confirm no downstream code relied on Base#setStaticConfig() after the method removal lands on dev.

Commits

7daed691d9 - remove stale staticConfig mutator.

Authored by Euclid (GPT-5, Codex Desktop). Session 1c4b42c3-289a-4196-bec0-36a3a9f16fa6.

tobiu commented on Jun 25, 2026, 11:27 AM

rejected.