Disclaimer: This project is not affiliated with, endorsed by, or associated with OpenClaw. It is an independent .NET implementation inspired by their work.
OpenClaw.NET is a NativeAOT-friendly AI agent runtime and gateway for .NET with practical OpenClaw ecosystem compatibility.
It is for .NET developers and operators who want a local or self-hosted agent gateway with explicit diagnostics, first-party .NET tools, OpenAI-compatible HTTP surfaces, and a path from source checkout to NativeAOT release artifacts.
Docs:AgentQi.dev is the documentation and ecosystem home for OpenClaw.NET. OpenClaw.NET remains the current runtime and repository identity.
AgentQi Documentation
AgentQi is the broader developer-infrastructure direction behind OpenClaw.NET: practical, observable, self-hosted AI agent systems for .NET developers.
OpenClaw.NET is the runtime and repository you can use today. AgentQiX is the likely future runtime identity.
NativeAOT-friendly runtime and gateway for .NET agent workloads
Agent runtime with tool execution, streaming, cancellation, retry, memory, and session support
Gateway with chat UI, admin UI, OpenAI-compatible endpoints, MCP, websocket, health, and diagnostics
First-class optional Microsoft Agent Framework adapter for Runtime.Orchestrator=maf without a special build
Durable workflow delegation through supported workflow backends such as maf-durable-http
CLI and Companion setup flows for source checkouts and desktop bundles
48 native tools covering file ops, sessions, memory, web, messaging, home automation, databases, email, and more
9 channel adapters (Telegram, SMS, WhatsApp, Teams, Slack, Discord, Signal, email, webhooks) with DM policy, allowlists, and signature validation
Native LLM providers for OpenAI, Claude, Gemini, Azure OpenAI, Ollama, and OpenAI-compatible endpoints
Optional embedded local models with Gemma 4 GGUF packages, package install/verify CLI commands, supervised sidecar inference, and frame-based video understanding
Practical reuse of existing OpenClaw TS/JS plugins and SKILL.md packages
Each desktop bundle includes Companion, the NativeAOT gateway, and the NativeAOT CLI.
Extract the archive.
Launch Companion from the companion folder.
Open the Setup tab.
Choose a provider/model and enter the provider key, choose Ollama for a local model server, or choose Embedded for an OpenClaw-managed local model such as Gemma 4.
Click Set Up and Start.
Companion writes a local config, starts the bundled gateway on 127.0.0.1, and connects to it. The current Windows and macOS release archives are unsigned, so first-run OS warnings are expected. See docs/RELEASES.md for checksums, standalone CLI/gateway archives, signing status, and maintainer release flow.
Quickstart
For a real local gateway from source:
export MODEL_PROVIDER_KEY="sk-..."
dotnet run --project src/OpenClaw.Cli -c Release -- start
When the gateway finishes startup it now prints explicit phase markers, a final OpenClaw gateway ready. block, the localhost URLs, Ctrl-C to stop, and any non-fatal startup notices under Started with notices:. Then open:
The root URL redirects to /chat. For the full first-run walkthrough (including the "First 10 Minutes" runbook and debugging flow), see docs/QUICKSTART.md. For the project shape and repository map before changing code, see docs/GETTING_STARTED.md.
If you want a direct gateway fallback instead of the full CLI onboarding flow, run:
dotnet run --project src/OpenClaw.Gateway -c Release -- --quickstart
--quickstart is interactive-only. It applies a minimal loopback-local profile for the current process, prompts for missing provider inputs, retries on the common first-run failures, and after a successful start can save the working setup to ~/.openclaw/config/openclaw.settings.json.
If the CLI is already on your PATH, the same guided entrypoints are:
OpenClaw.NET now treats Ollama as a first-class native provider at http://127.0.0.1:11434. Older /v1 endpoints still work for one compatibility cycle, but openclaw models doctor will flag them so you can migrate cleanly.
For OpenClaw-managed local inference, use provider embedded with an installable package. Gemma 4 is now the main embedded local model path:
The package catalog includes Gemma 4 E2B, E4B, 31B, and 26B-A4B GGUF entries, plus the experimental Gemma 4 E2B LiteRT-LM package for adapter work. The older gemma-local-small-q4 Gemma 3 package remains available for smaller machines.
Embedded video support is frame-based: OpenClaw samples local video/* inputs into ordered image frames before calling the local sidecar, and Gemma 4 GGUF packages include the multimodal projector file needed for image-frame inputs. LiteRT-LM packages are experimental and require an OpenClaw-compatible adapter binary; see docs/LOCAL_MODELS.md.
Breaking change: browser admin usage is account/session-first. Use named operator accounts for /admin, and use operator account tokens for Companion, CLI, API, and websocket clients.
Security
When binding to a non-loopback address, the gateway refuses to start unless dangerous settings are explicitly hardened (auth token required, tool
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
