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	9562
title	Implement Generic OIDC Discovery and Google OAuth Hands-on Guide
state	Closed
labels	documentationenhancementdeveloper-experienceai
assignees	tobiu
createdAt	Mar 26, 2026, 3:39 PM
updatedAt	Mar 26, 2026, 3:55 PM
githubUrl	https://github.com/neomjs/neo/issues/9562
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 26, 2026, 3:55 PM

Implement Generic OIDC Discovery and Google OAuth Hands-on Guide

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

Closed v12.1.0 documentationenhancementdeveloper-experienceai

tobiu commented on Mar 26, 2026, 3:39 PM

Enhance the MCP server authorization to support generic OIDC providers and provide a concrete "hands-on" guide for Google OAuth integration.

Goal: Enable developers to secure Neo.mjs MCP servers using public identity providers without needing to understand the underlying URL structures.

Scope:

Code Enhancement:
- Update aiConfig.mjs to support AUTH_ISSUER_URL.
- In Server.mjs, implement OIDC Discovery: fetch {issuer}/.well-known/openid-configuration to dynamically resolve token_endpoint, introspection_endpoint, etc.
- Retain the existing Keycloak-path logic as a fallback for AUTH_REALM based configs.
Hands-on Guide:
- Create learn/guides/mcp/GoogleAuthDemo.md.
- Provide step-by-step setup for Google Cloud Console (Client ID/Secret, Authorized Redirect URIs).
- Show the exact .env configuration needed.
- Explain the "Audience" mapping for Google (which can be tricky).

tobiu added the documentation label on Mar 26, 2026, 3:39 PM

tobiu added the enhancement label on Mar 26, 2026, 3:39 PM

tobiu added the developer-experience label on Mar 26, 2026, 3:39 PM

tobiu added the ai label on Mar 26, 2026, 3:39 PM

tobiu assigned to @tobiu on Mar 26, 2026, 3:39 PM

tobiu referenced in commit 4251c45 - "Implement OIDC discovery and add Google OAuth demo guide (#9562)" on Mar 26, 2026, 3:54 PM

tobiu closed this issue on Mar 26, 2026, 3:55 PM

tobiu Mar 26, 2026, 3:55 PM

Implemented dynamic OIDC discovery via AUTH_ISSUER_URL. Created Google OAuth hands-on guide and updated navigation. Verified with functional tests.