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	7858
title	Documentation: Comprehensive Guide for GitHub Workflow MCP Server
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Nov 22, 2025, 4:42 PM
updatedAt	Nov 22, 2025, 5:07 PM
githubUrl	https://github.com/neomjs/neo/issues/7858
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 22, 2025, 5:07 PM

Documentation: Comprehensive Guide for GitHub Workflow MCP Server

Closed v11.9.0/archive-v11-9-0-chunk-1 documentationenhancementai

tobiu commented on Nov 22, 2025, 4:42 PM

Enhance learn/guides/mcp/GitHubWorkflow.md to provide a deep dive into the neo.mjs-github-workflow MCP server.

Requirements:

Document all available tools: based on openapi.yaml (e.g., healthcheck, sync_all, create_issue, update_issue_relationship, etc.).
Explain the internal architecture: Detail the service layer and synchronization logic.
Deep Dive into SyncService: Explain the orchestration of IssueSyncer, ReleaseSyncer, and MetadataManager.
GraphQL Integration: Describe how GraphqlService is used for complex data fetching and mutations.
Update Core Sections: Revise "Purpose" and "Workflow" to accurately reflect the current code implementation.

Source Files to Analyze:

ai/mcp/server/github-workflow/openapi.yaml
ai/mcp/server/github-workflow/services/SyncService.mjs
ai/mcp/server/github-workflow/services/sync/*.mjs
ai/mcp/server/github-workflow/services/*.mjs

tobiu Nov 22, 2025, 5:06 PM

Input from Gemini 2.5 pro:

✦ I have added section "7. Platform Independence & Vendor Lock-In" to the guide.

This section explicitly addresses the strategic value of the local-first architecture:

Sovereignty: Highlighting that git repos don't natively store issues/releases.

Microsoft/Azure Context: Acknowledging the ownership risk.

Migration Path: Explaining how local Markdown files make moving to GitLab/Gitea feasible.

Source of Truth: Re-framing GitHub as a "sync target" rather than the primary data store.

The guide is now complete and covers technical, operational, and strategic aspects of the server.