What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	8456
title	Automate Release Workflow with Git Squash & Local-First Strategy
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Jan 9, 2026, 11:09 AM
updatedAt	Jan 9, 2026, 11:17 AM
githubUrl	https://github.com/neomjs/neo/issues/8456
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 11:17 AM

Automate Release Workflow with Git Squash & Local-First Strategy

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.19.1 enhancementaibuild

tobiu commented on Jan 9, 2026, 11:09 AM

To streamline the release process, ensure releases.json is accurate, and automate the "Squash to Main" pattern, we will create a comprehensive release script.

Context:

Releases are based on the dev branch.
main branch is used solely for an atomic squash commit of the release cycle.
releases.json must be up-to-date in the published package.
Tickets must be archived after the release.

1. Expose Sync Service Modify ai/services.mjs to export GH_SyncService (mapping to ai/mcp/server/github-workflow/services/SyncService.mjs) to enable scriptable syncs.

2. Create buildScripts/publishRelease.mjs This script will automate the following workflow:

Pre-flight Checks:
- Ensure current branch is dev.
- Ensure gh CLI is authenticated.
- Verify resources/content/release-notes/vX.Y.Z.md exists.
Prepare (Dev):
- Run buildScripts/prepareRelease.mjs (updates version, SEO, releases.json).
- Stage and Commit changes to dev (Message: "Release vX.Y.Z").
- Push dev.
Squash to Main (Atomic History):
- Checkout main.
- git merge --squash dev.
- Auto-resolve conflicts by accepting "theirs" (the dev version).
- Commit (Message: "vX.Y.Z").
- Push main.
- Capture Hash: Store the new commit hash from main.
Finalize Notes (Dev):
- Checkout dev.
- Append the main commit hash to the local release notes (e.g., "Atomic Changelog: [Hash]").
- Commit and Push dev.
Release (GitHub):
- Execute gh release create vX.Y.Z --target dev --title "vX.Y.Z" --notes-file resources/content/release-notes/vX.Y.Z.md.
- This triggers the npm-publish Action (from dev).
Post-Release Cleanup:
- Wait for release propagation.
- Run GH_SyncService.runFullSync() to archive tickets into resources/content/issue-archive/vX.Y.Z/.
- Commit and Push dev.

tobiu added the enhancement label on Jan 9, 2026, 11:09 AM

tobiu added the ai label on Jan 9, 2026, 11:09 AM

tobiu added the build label on Jan 9, 2026, 11:09 AM

tobiu Jan 9, 2026, 11:12 AM

Input from Gemini 3 Pro:

✦ Refinement: After running buildScripts/prepareRelease.mjs, we must also execute npm run build-all to ensure all production artifacts are compiled with the new version. This step should be added to the 'Prepare (Dev)' phase.

tobiu assigned to @tobiu on Jan 9, 2026, 11:16 AM

tobiu referenced in commit e68dd7b - "feat: Add publishRelease.mjs script for local-first release workflow (#8456)" on Jan 9, 2026, 11:16 AM

tobiu Jan 9, 2026, 11:16 AM

Input from Gemini 3 Pro:

✦ Implemented the buildScripts/publishRelease.mjs script to automate the local-first release workflow.

Key Changes:

Exposed GH_SyncService: Modified ai/services.mjs to export the sync service, enabling the release script to trigger ticket archiving programmatically.

Created Release Script: buildScripts/publishRelease.mjs now handles:

Pre-flight Checks: Verifies branch (dev), auth, and release notes.

Preparation: Runs prepareRelease.mjs and npm run build-all.

Atomic History: Squashes dev changes into main for a clean release history.

Release Creation: Uses gh release create with local artifacts.

Post-Release Sync: Automatically archives closed tickets to resources/content/issue-archive/vX.Y.Z/ and commits the changes.

The workflow is now fully automated and ensures releases.json and ticket archives are synchronized with the published package.

tobiu closed this issue on Jan 9, 2026, 11:17 AM