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	14777
title	feat(fleet): surface avatarUrl in the fleet cockpit DTO — the AgentCard avatar-data bridge
state	Closed
labels	[]
assignees	neo-opus-vega
createdAt	3:34 PM
updatedAt	3:51 PM
githubUrl	https://github.com/neomjs/neo/issues/14777
author	neo-opus-vega
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	3:51 PM

feat(fleet): surface avatarUrl in the fleet cockpit DTO — the AgentCard avatar-data bridge

Closed Backlog/active-chunk-4 []

neo-opus-vega commented on 3:34 PM

Sub of #14598 (FM cockpit AgentCard) · Refs #14560 (FM cockpit UI/UX epic) · Refs #14755 (card component, PR #14774)

The per-agent avatar pipeline is one bridge away from end-to-end. VBA this turn:

Storage ✓ — FleetManager.setAvatar({id, avatarUrl}) persists metadata.avatarUrl on the agent's registry definition (ai/services/fleet/FleetManager.mjs:257).
Render ✓ — the AgentCard (PR #14774) binds a profile-avatar Image to the provider's avatarUrl.
Missing bridge — the fleet cockpit DTO (src/ai/fleet/fleetCockpitStatus.mjs) does NOT hoist avatarUrl into the row. It hoists the other display fields flat (displayName, githubUsername, harnessType) but not the avatar, so the card-wall has no clean row.avatarUrl to bind each card to.

Scope

Hoist avatarUrl: publicAgent.metadata?.avatarUrl ?? null into the DTO row (beside displayName), matching the existing flat-contract pattern. Source verified: sanitizePayload preserves metadata recursively (fleetCockpitStatus.mjs:156), so publicAgent.metadata.avatarUrl is available at the row builder.

Acceptance Criteria

The fleet cockpit DTO row carries a top-level avatarUrl (from metadata.avatarUrl, null when unset).
Unit spec: a row surfaces avatarUrl when the agent def has metadata.avatarUrl, and null when it does not (no undefined leak).
Purely additive — no change to the other row fields.

Freshness

Live open-issue search "avatar cockpit DTO" → no existing ticket (this turn); latest open ~#14773.

Filed by Vega (@neo-opus-vega · Claude Opus 4.8).