The Application Engine for the AI Era

🚀 True Multithreading Meets Context Engineering — Build Desktop-Class UIs with an AI Co-Developer.

⚡ The Mental Model: Neo.mjs is a multi-threaded application runtime where UI components are persistent objects—not ephemeral render results. This architectural shift enables desktop-class performance, multi-window orchestration, and AI-driven runtime mutation that traditional frameworks cannot achieve.

💻 Neo.mjs is not a framework; it is an Application Engine for the web. Just as Unreal Engine provides a complete runtime and toolchain for games, Neo.mjs provides a multi-threaded runtime and AI-native toolchain for enterprise applications.

Imagine web applications that never jank, no matter how complex the logic, how many real-time updates they handle, or how many browser windows they span. Neo.mjs is engineered from the ground up to deliver desktop-like fluidity and scalability. While it excels for Single Page Apps (SPAs), Neo.mjs is simply the best option for browser-based multi-window applications, operating fundamentally different from traditional frameworks.

By leveraging a pioneering Off-Main-Thread (OMT) architecture, Neo.mjs ensures your UI remains butter-smooth. The main thread is kept free for one purpose: flawless user interactions and seamless DOM updates.

But performance is only half the story. With v11, Neo.mjs becomes the world's first AI-native frontend platform, designed to be developed with AI agents as first-class partners in your workflow.

🎯 Is Neo.mjs Right for You?

Neo.mjs is an Application Engine, not a website builder. It is a mature, enterprise-grade platform with over 130,000 lines of production-ready code.

✅ Perfect For:

Financial & Trading Platforms: processing 10k+ ticks/sec without UI freeze.
Multi-Window Workspaces: IDEs, Control Rooms, and Dashboards that span multiple screens.
AI-Native Interfaces: Apps where the UI structure must be mutable by AI agents at runtime.
Enterprise SPAs: Complex logic that demands the stability of a desktop application.

❌ Not Designed For:

Static content sites or simple blogs (Use Astro/Next.js).
Teams looking for "React with a different syntax."
Developers unwilling to embrace the Actor Model (Workers).

🚀 The AI-Native Development Platform

Neo.mjs v11 introduces a revolutionary approach to software development: Context Engineering. We've moved beyond simple "AI-assisted" coding to create a truly AI-native platform where AI agents are deeply integrated partners in the development process. This is made possible by a suite of dedicated Model Context Protocol (MCP) servers that give agents the context they need to understand, build, and reason about your code.

This isn't just about generating code; it's about creating a self-aware development environment that accelerates velocity, improves quality, and enables a new level of human-AI collaboration.

🧠 The Knowledge Base Server: Gives agents a deep, semantic understanding of your project. Powered by ChromaDB and Gemini embeddings, it allows agents to perform semantic searches across your entire codebase, documentation, and historical tickets. An agent can ask, "How does VDOM diffing work?" and get the exact source files and architectural guides relevant to the currently checked-out version.
- 📘 Read the Guide
💾 The Memory Core Server: Provides agents with persistent, long-term memory. Every interaction—prompt, thought process, and response is stored, allowing the agent to learn from experience, recall past decisions, and maintain context across multiple sessions. This transforms the agent from a stateless tool into a true collaborator that grows with your project.
- 📘 Read the Guide
🤖 The GitHub Workflow Server: Closes the loop by enabling agents to participate directly in your project's lifecycle. It provides tools for autonomous PR reviews, issue management, and bi-directional synchronization of GitHub issues into a local, queryable set of markdown files. This removes the human bottleneck in code review and project management.
- 📘 Read the Guide
⚡️ The Agent Runtime: Empower your agents to act as autonomous developers. Instead of passively asking for information, agents can write and execute complex scripts using the Neo.mjs AI SDK. This enables advanced workflows like self-healing code, automated refactoring, and data migration—running locally at machine speed.
- 📘 Read the Guide

Why an Engine Architecture Matters for AI

AI agents are "blind" in traditional compiled frameworks (React, Svelte) because the code they write (JSX/Templates) is destroyed by the build step—the runtime reality (DOM nodes) looks nothing like the source.

In Neo.mjs, the map IS the territory. Because components are persistent objects in the App Worker (not ephemeral DOM nodes), the AI can query their state, methods, and inheritance chain at any time. It's like inspecting a running game character in Unreal Engine, rather than parsing the pixels on the screen. The AI sees exactly what the engine sees, enabling it to reason about state, inheritance, and topology with perfect accuracy. Furthermore, the Neural Link allows agents to query the runtime for the Ground Truth, enabling them to verify reality and solve complex, runtime-dependent problems that static analysis cannot touch.

This powerful tooling, co-created with AI agents, enabled us to ship 388 architectural enhancements in just 6 weeks. This order-of-magnitude increase in velocity proves that Context Engineering solves the complexity bottleneck. To learn more about this paradigm shift, read our blog post: 388 Tickets in 6 Weeks: Context Engineering Done Right.

🔗 The Neural Link: Your App is a Living Graph

Most frameworks offer a "Read-Only" view of your code to AI. Neo.mjs offers "Read/Write" access to the Runtime.

Because Neo.mjs components are persistent objects (Lego Technic) rather than transient DOM nodes (Melted Plastic), the Neural Link allows AI agents to connect directly to the engine's memory.

Introspection: Agents can query the Scene Graph (get_component_tree) to understand the exact state of the UI.
Mutation: Agents can hot-patch class methods, modify state, or re-parent components in real-time without a reload.
Verification: Agents can simulate user events (clicks, drags) to verify their own fixes.

📘 Read the Neural Link Guide

🚀 Jump In: Your First Neo.mjs App in Minutes

Run this command:

npx neo-app@latest

This one-liner sets up everything you need to start building with Neo.mjs, including:

A new app workspace.
A pre-configured app shell.
A local development server.
Launching your app in a new browser window — all in one go.

:book: More details? Check out our Getting Started Guide

:student: Make sure to dive into the Learning Section

Next steps:

:star: Experience stunning Demos & Examples here: Neo.mjs Examples Portal
Many more are included inside the repos apps & examples folders.
:blue_book: All Blog Posts are listed here: Neo.mjs Blog
:robot: Get started with the **[AI Knowledge Base Quick Start Guide](./.github/AI_QUICK_START.

Neo

Install / Use

README