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	7886
title	[AI] Streamline create_issue workflow instruction
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Nov 23, 2025, 8:29 PM
updatedAt	Nov 23, 2025, 8:30 PM
githubUrl	https://github.com/neomjs/neo/issues/7886
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 23, 2025, 8:30 PM

[AI] Streamline create_issue workflow instruction

Closed v11.10.0/archive-v11-10-0-chunk-1 documentationenhancementai

tobiu commented on Nov 23, 2025, 8:29 PM

Description

Updates the create_issue tool description in ai/mcp/server/github-workflow/openapi.yaml to streamline the proposal workflow.

Changes

Modified step 4 of the Mandatory Workflow for create_issue.
Old: "Only after displaying the proposal, call create_issue."
New: "Immediately call create_issue after displaying the proposal. Do not ask for permission first (the user can decline the tool call)."

Reason

To improve workflow efficiency. Agents should display the proposal and then immediately trigger the tool, relying on the native tool confirmation UI for user approval/rejection, rather than adding an extra conversational turn to ask for permission.

Acceptance Criteria

The openapi.yaml file reflects the updated instruction.
Future agent sessions follow the "Show -> Call" pattern without redundant permission questions.

tobiu added the documentation label on Nov 23, 2025, 8:29 PM

tobiu added the enhancement label on Nov 23, 2025, 8:29 PM

tobiu added the ai label on Nov 23, 2025, 8:29 PM

tobiu assigned to @tobiu on Nov 23, 2025, 8:30 PM

tobiu referenced in commit 4cb4534 - "[AI] Streamline create_issue workflow instruction #7886" on Nov 23, 2025, 8:30 PM

tobiu closed this issue on Nov 23, 2025, 8:30 PM