A self-hosted AI agent runtime for .NET, with a desktop companion for everyday use.
Download desktop · Run from source · Documentation · Compatibility · 中文
Run an assistant locally or host a gateway for your team. Connect a hosted or local model, give it tools and memory, and work through desktop chat, the browser, messaging channels, or APIs. Developers can extend the runtime in .NET and deploy supported capabilities with NativeAOT.
OpenClaw.NET is the runtime and repository. AgentQi [OpenClaw.NET] is the Avalonia desktop companion; AgentQi.dev is the documentation and ecosystem home.
This is an independent .NET implementation inspired by OpenClaw, with practical ecosystem compatibility. It is not affiliated with or endorsed by the upstream project.
Chat is the starting point. AgentQi brings setup, connections, activity, memory, history, and settings into one desktop interface, with light and dark themes.
Companion welcome screen from main, before connecting a gateway. Packaged releases may show an earlier interface.
- Set up through the app: choose a provider and model, enter credentials in dedicated fields, and start a local gateway.
- Describe a settings change: use
/configure set the session timeout to 45 minutes, review the proposed values, then apply or cancel. - Use the GUI when you prefer: the manual settings editor works without a language model when the gateway is reachable; advanced setup is available when needed.
Chat configuration covers supported scalar settings, not every operation. Credentials, provider setup, and complex account objects retain dedicated forms. See what can be configured through chat.
Choose a desktop bundle from the latest release. Each includes Companion, the NativeAOT gateway, and the NativeAOT CLI.
| Platform | Download |
|---|---|
| Windows x64 | openclaw-desktop-win-x64.zip |
| Apple Silicon macOS | openclaw-desktop-osx-arm64.zip |
| Linux x64 | openclaw-desktop-linux-x64.zip |
- Extract the archive and launch Companion from the
companionfolder. - Open Setup. In the redesigned Companion, you can also choose Set up my assistant in Chat.
- Choose your provider and model. Enter a hosted provider key, or choose Ollama for a local model server.
- Click Set Up and Start.
Companion writes a local configuration, starts the bundled gateway on 127.0.0.1, and connects to it. Embedded local inference is also available; see the local model guide for package installation and requirements.
The Windows and macOS release archives are currently unsigned. See the release guide for first-run OS warnings, checksums, standalone CLI/gateway downloads, and signing status. The screenshot above shows development on main; check release notes for the features included in your download.
Install Git and the .NET 10 SDK, then clone the repository:
git clone https://github.com/clawdotnet/openclaw.net
cd openclaw.netFor the default hosted-provider path, set your API key and start the guided setup. These commands use Bash or zsh:
export MODEL_PROVIDER_KEY="sk-..."
dotnet run --project src/OpenClaw.Cli -c Release -- startIn PowerShell, set the key with $env:MODEL_PROVIDER_KEY = "sk-...", then run the same dotnet command. To use another provider or a local model, follow the provider setup guide.
The CLI runs setup if needed, saves the local configuration, and launches the gateway. Wait for OpenClaw gateway ready., then open:
| Surface | Address |
|---|---|
| Browser chat | http://127.0.0.1:18789/chat |
| Administration | http://127.0.0.1:18789/admin |
| Integration status API | http://127.0.0.1:18789/api/integration/status |
| MCP endpoint | http://127.0.0.1:18789/mcp |
Use named operator accounts for browser administration and operator account tokens for Companion, CLI, API, and WebSocket clients. The quickstart covers the full first-run walkthrough and troubleshooting.
To try the Avalonia Companion from the same checkout:
dotnet run --project src/OpenClaw.Companion -c ReleaseConnect it to your running gateway through Setup & runtime. See Companion token storage for authentication and credential handling.
From the repository root, this deterministic sample demonstrates the runtime loop and tool invocation without a model server, Docker, or a browser:
dotnet restore OpenClaw.Net.slnx
dotnet build OpenClaw.Net.slnx --configuration Release --no-restore
dotnet run --project samples/OpenClaw.HelloAgent -c Release --no-buildExpected output:
OpenClaw.HelloAgent
User: hello
Agent: hello from OpenClaw.NET
Tool: echo(hello): ok
| Area | Capabilities |
|---|---|
| Agent runtime | Streaming, tool execution, cancellation, retries, sessions, memory, and token-usage reporting. |
| Interfaces | AgentQi desktop companion, browser chat and admin UI, CLI, terminal UI, OpenAI-compatible HTTP endpoints, MCP, and WebSockets. |
| Models | OpenAI, Claude, Gemini, Azure OpenAI, DeepSeek, Ollama, and OpenAI-compatible providers; named profiles and optional embedded local inference. |
| Tools and channels | 80+ native and optional tool surfaces for files, web, sessions, databases, email, home automation, and more; adapters for Telegram, WhatsApp, Teams, Slack, Discord, and other channels. The active set depends on configuration. |
| Extensions | MCP servers and interactive MCP Apps, reusable SKILL.md packages, first-party .NET integrations, and supported OpenClaw TS/JS plugins. |
| Long-running work | Session-scoped /goal continuation, /loop recurring prompts, and optional durable workflow backends. |
| Review and observability | Tool approvals, diagnostics, audit and trajectory exports, passive harness contracts, evidence bundles, and optional Plan-Execute-Verify execution. |
| Developer tooling | Offline harness regression checks, static codebase maps, SkillKit authoring and validation, and TokenJuice tool-output reduction. |
Explore the user guide, tool catalog, SkillKit, and harness testing for details. The separate AgentQi Mobile repository provides an Android operator console and build instructions.
NativeAOT support and upstream compatibility depend on the feature you enable. Check the capability matrix and compatibility guide before choosing a deployment lane.
| Lane | Examples |
|---|---|
| Core | Runtime loop, gateway, CLI, OpenAI-compatible API, and NativeAOT-friendly host path. |
| Optional | Companion, channel adapters, browser/MQTT packages, model integrations, and workflow backends. |
| Experimental | Embedded local model sidecars and adapter-oriented package paths. |
| JIT-only | Dynamically loaded native .NET plugins. |
For framework and agent interoperability, see Microsoft Agent Framework, A2A, and workflow backends. For interactive MCP App hosting, use the documented gateway host routes.
Local setup binds the gateway to loopback. Before exposing it beyond your machine, read SECURITY.md: the gateway refuses unsafe public-bind configurations until required authentication and tooling restrictions are in place.
Outbound web fetches and browser navigations use URL safety checks by default, including restrictions on private, loopback, link-local, and metadata destinations. See the security guide before changing those policies.
For private access while keeping the gateway on 127.0.0.1, use Tailscale Serve:
openclaw setup tailscale serveThis command assumes the CLI is on your PATH; from a checkout, use dotnet run --project src/OpenClaw.Cli -c Release -- setup tailscale serve.
Browse AgentQi.dev or the complete repository documentation index.
| Start here | What you will find |
|---|---|
| Evaluator overview | What the project does and how to evaluate it. |
| Quickstart | First-run setup, provider examples, diagnostics, and recovery. |
| Getting started | Repository map, architecture, and contributor setup. |
| User guide | Providers, tools, skills, memory, channels, and daily operation. |
| Companion chat configuration | Supported settings, review/apply behavior, and advanced setup. |
| Releases | Downloads, checksums, signing status, and release procedures. |
| Capability matrix | Core, optional, experimental, and JIT-only features. |
| Local models | Embedded model packages, sidecars, and frame-based video support. |
| Architecture boundaries | Runtime, gateway, extension, and AOT/JIT boundaries. |
| Roadmap | Planned work and current priorities. |
| 中文文档 | Simplified Chinese first-run orientation. |
Contributions are welcome, especially security reviews, NativeAOT improvements, channel adapters, and performance benchmarks. Start with CONTRIBUTING.md.
See project governance, maintainer roles, and the review checklist for contribution and review expectations.