N.E.O. — Native Executable Orchestrator

AI-powered tool builder — describe what you need in natural language, and N.E.O. generates, compiles, and runs it in real time.

Think Claude Artifacts or ChatGPT Canvas — but for native .NET apps on your own machine, with a real GUI (WPF or Avalonia) or a browser tab.

Status: Pre-alpha (v0.000000000001). Hobby project, MIT-licensed.

Try it with one prompt

"Build an app that captures the system's audio output in real time via WASAPI and generates a techno-club visualizer reacting to frequency, volume, bass and beats."

---

Three ways to run Neo

Surface	Who drives	Where it runs	Setup
Desktop host	You type prompts into Neo.App	Native window (WPF or Avalonia)	Getting Started
MCP server	Claude Code / Cowork drives	Neo controls a child window	MCP Server
Web app	You type prompts into a browser	Avalonia-in-WASM + local ASP.NET backend	Web App

All three share the same Neo.App.Core (compile pipeline, agents, structured-response contract). Pick whichever fits your workflow — they're not mutually exclusive.

Quickstart

Prerequisites

• .NET 9 SDK (change NeoNetMajor in Directory.Build.props if you're on a different major).
• One AI provider env var, or a local model (Ollama, LM Studio). Neo reads keys from user env vars — nothing is stored in the repo.

Provider	Env var
Anthropic Claude	ANTHROPIC_API_KEY
Google Gemini	GEMINI_API_KEY
OpenAI	OPENAI_API_KEY
Ollama	OLLAMA_HOST (e.g. http://localhost:11434)
LM Studio	LMSTUDIO_HOST (e.g. http://localhost:1234)

Desktop host (WPF or Avalonia)

git clone https://github.com/hf75/N.E.O.git
cd N.E.O
# Windows — includes the WPF host:
dotnet run --project Neo.App
# Cross-platform — Avalonia:
dotnet run --project Neo.App.Avalonia

MCP server (Claude Code / Cowork)

dotnet build Neo.McpServer -c Release
dotnet build Neo.PluginWindowAvalonia.MCP -c Release

Then register the server in .claude/settings.json — full details in docs/wiki/MCP-Server.md.

Web app (browser)

# 1. Publish the Avalonia.Browser client once
dotnet publish Neo.App.WebApp/Neo.App.WebApp.Browser/Neo.App.WebApp.Browser.csproj \
    -c Release -o Neo.App.WebApp/Neo.App.WebApp.Browser/bin/Release/net9.0-browser/publish

# 2. Run the backend (serves the WASM bundle + proxies AI + NuGet)
dotnet run --project Neo.Backend -c Release --urls=http://localhost:5099

Open http://localhost:5099. Full guide: docs/wiki/Web-App.md.

---

What it does

• Prompt → code → live UI in seconds. Claude/GPT/Gemini writes C#; Roslyn compiles; a collectible AssemblyLoadContext loads it into a plugin window (desktop) or the same WASM runtime (web).
• Iterate. Follow-up prompts see the previous code and produce full updates (desktop/MCP also support unified-diff patches).
• Branching undo/redo, visual designer (WPF), export to standalone .exe (Win/Linux/macOS), AppContainer sandbox (WPF).
• Session save/load as .neo files — same format across desktop, MCP, and Web App.
• Built-in AI capabilities: image generation (Gemini), image analysis (Gemini), speech-to-text (Whisper), text-to-speech (OpenAI TTS).
• Optional Python integration via embedded Python 3.11 (desktop only).
• Live-MCP — every generated app is itself an MCP server. Annotate methods with [McpCallable] and properties with [McpObservable] and Claude Code can call them directly, read state, subscribe to changes. Works in two modes: live inside N.E.O. (Dev-Mode) or as a standalone exported .exe (Frozen-Mode) that anyone can register with claude mcp add.
• Channel back-reporting — generated apps can push prompts back into Claude Code to drive business logic without pre-coding. Combined with Live-MCP, this closes the loop: Claude drives the app, the app drives Claude.
• Excel MCP — a second MCP server that gives Claude read/write access to the active Excel workbook via an in-process COM add-in.

Architecture at a glance

           Desktop host         MCP server          Web app (browser)
       +----------------+   +----------------+   +------------------+
       |  Neo.App       |   |  Neo.McpServer |   |  Neo.App.WebApp  |
       |  Neo.App.Avalonia|  (driven by Claude)  |  (Avalonia WASM) |
       +--------+---------+---------+----------+---------+---------+
                           |                             |
                +----------+----------+       +----------+-----------+
                |   Neo.App.Core      |       |  Neo.Backend         |
                |   (prompt→DLL path) |       |  (AI+NuGet proxy,    |
                |                     |       |   serves wwwroot)    |
                +----------+----------+       +----------------------+
                           |
          +----------------+-----------------+
          | Neo.AssemblyForge (compile pipe) |
          | Neo.Agents.* (AI providers)      |
          | Neo.IPC (Named Pipes; desktop)   |
          +----------------------------------+

Full developer-facing map: docs/wiki/Architecture.md.

Documentation

Everything lives in docs/wiki/. Start with Home or jump straight to the surface you care about:

• Getting Started — install, first prompt (desktop host path)
• Web App — the browser variant
• MCP Server — Claude-driven workflow (25 tools)
• Live-MCP — generated apps as MCP servers (call into them, read state, subscribe)
• Frozen-Mode — exporting Live-MCP apps as standalone executables
• Excel MCP — live Excel integration
• Channels — generated apps that push prompts back to Claude
• Architecture — how the projects fit together
• Features Overview · Designer Mode · Export and Import · Settings · Shortcuts · Troubleshooting

License

MIT — see LICENSE.