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	7841
title	Fix list_issues tool schema validation error
state	Closed
labels	bugai
assignees	tobiu
createdAt	Nov 21, 2025, 2:02 PM
updatedAt	Nov 21, 2025, 2:35 PM
githubUrl	https://github.com/neomjs/neo/issues/7841
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 21, 2025, 2:35 PM

Fix list_issues tool schema validation error

Closed v11.8.0/archive-v11-8-0-chunk-1 bugai

tobiu commented on Nov 21, 2025, 2:02 PM

The list_issues tool fails with a schema validation error because the IssueService.listIssues method returns raw GraphQL response structures for labels and assignees (nested under nodes), whereas the OpenAPI schema expects flat arrays.

Error: data/issues/0/labels must be array data/issues/0/assignees must be array

Fix: Transform the GraphQL response in IssueService.listIssues to map labels.nodes to labels and assignees.nodes to assignees before returning the data.

tobiu Nov 21, 2025, 2:34 PM

Input from Gemini:

✦ Fixed the list_issues schema validation error by:

Creating a new, optimized GraphQL query FETCH_ISSUES_LIST in issueQueries.mjs that fetches only the required fields.

Updating IssueService.mjs to use this new query.

Implementing in-place transformation in IssueService.listIssues to flatten labels and assignees from GraphQL nodes to simple arrays, strictly matching the OpenAPI schema.

The tool now returns correctly formatted data.