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	12209
title	Make portal content cross-link URLs per-content-type config
state	Closed
labels	enhancementairefactoring
assignees	neo-opus-ada
createdAt	May 30, 2026, 7:25 PM
updatedAt	Jun 1, 2026, 10:44 AM
githubUrl	https://github.com/neomjs/neo/issues/12209
author	neo-opus-ada
commentsCount	1
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12208 Extract the shared timeline contract into Neo.app.content.Component
blocking	[x] 12211 Portal Discussion view — Portal.view.news.discussions (thin subclass)
closedAt	Jun 1, 2026, 10:44 AM

Make portal content cross-link URLs per-content-type config

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementairefactoring

neo-opus-ada commented on May 30, 2026, 7:25 PM

Context

Part of epic #12207 (foundation step 5). The generic content Component hardcodes ticket cross-link assumptions, which would mis-link PR/Discussion content.

The Fix

Remove the hardcoded issuesUrl '#/news/tickets/' default from the generic src/app/content/Component.mjs, and the commitsUrl / release-badge assumptions from tickets/Component.mjs; make cross-link URLs a per-content-type config so PR and Discussion content resolve correct links. Additive — the existing Tickets tab keeps its current links via its own config.

Acceptance Criteria

Cross-link URLs are per-type configurable; Tickets tab links unchanged.

Epic #12207. Depends on foundation step 4; unblocks the per-type views.

tobiu referenced in commit e9600ea - "refactor(portal): make content cross-link URLs per-content-type config (#12209) (#12292) on Jun 1, 2026, 10:44 AM

tobiu closed this issue on Jun 1, 2026, 10:44 AM

tobiu referenced in commit c35256b - "feat(portal): Pull Requests news view — Portal.view.news.pulls (#12213) (#12287) on Jun 1, 2026, 10:52 AM

Make portal content cross-link URLs per-content-type config

Context

The Fix

Acceptance Criteria

Related