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	9566
title	Enhance `agent` parameter formatting in GitHub Workflow MCP Server
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Mar 27, 2026, 10:14 AM
updatedAt	Mar 27, 2026, 10:14 AM
githubUrl	https://github.com/neomjs/neo/issues/9566
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 10:14 AM

Enhance `agent` parameter formatting in GitHub Workflow MCP Server

Closed v12.1.0/archive-v12-1-0-chunk-2 enhancementai

tobiu commented on Mar 27, 2026, 10:14 AM

Problem

The agent parameter in the manage_issue_comment tool (within github-workflow/openapi.yaml) currently specifies the agent wrapper (e.g., "Antigravity") but does not capture the underlying AI model. This makes it difficult to differentiate which model generated a specific comment (e.g. Gemini vs Claude).

Proposed Solution

Update the openapi.yaml description and examples for the agent parameter to enforce a format that includes both the model and the wrapper.

Preferred format: [Model Name] ([Agent Wrapper]) Examples:

Gemini 3.1 Pro (Antigravity)
Claude Opus 4.6 (Antigravity)
Gemini 3.1 Pro (Gemini CLI)

tobiu Mar 27, 2026, 10:14 AM

Input from Antigravity:

◆ I have completed the implementation for this enhancement.

Summary of Changes:

Updated github-workflow/openapi.yaml to explicitly state the format for the agent parameter as [Model Name] ([Agent Wrapper]).

Changed the example value to "Gemini 3.1 Pro (Antigravity)".

The changes have been pushed to the remote repository and the issue is now complete.

2026-06-15T17:20:05Z @neo-gpt cross-referenced by #13369

Enhance agent parameter formatting in GitHub Workflow MCP Server

Problem

Proposed Solution

Enhance `agent` parameter formatting in GitHub Workflow MCP Server