OpenClaw.NET

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 Companion is the Avalonia desktop product for OpenClaw.NET; 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.

Meet the desktop companion

Chat is the starting point. AgentQi Companion 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.

Download And Run Desktop

Choose a desktop bundle from the latest release. Each includes AgentQi Companion, the NativeAOT gateway, and the NativeAOT CLI.

1. Extract the archive and launch Companion from the companion folder.
2. Open Setup. In the redesigned Companion, you can also choose Set up my assistant in Chat.
3. Choose your provider and model. Enter a hosted provider key, or choose Ollama for a local model server.
4. 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.

Quickstart

Run a local gateway from source

Install Git and the .NET 10 SDK, then clone the repository:

git clone https://github.com/clawdotnet/openclaw.net
cd openclaw.net

For 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 -- start

In 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:

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 Release

Connect it to your running gateway through Setup & runtime. See Companion token storage for authentication and credential handling.

Try the runtime without an API key

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-build

Expected output:

OpenClaw.HelloAgent
User: hello
Agent: hello from OpenClaw.NET
Tool: echo(hello): ok

What Works Now

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.

For audience restrictions, verified bundle updates, remote device enrollment, and a one-command local demo, see the operations guide. Audience controls are opt-in; verified updates require an independently trusted publisher key, and remote device enrollment requires HTTPS and an administrator-issued code.

Compatibility and capability boundaries

NativeAOT support and upstream compatibility depend on the feature you enable. Check the capability matrix and compatibility guide before choosing a deployment lane.

For framework and agent interoperability, see Microsoft Agent Framework, A2A, and workflow backends. For direct MetaSkill API calls, see the MetaSkill invocation API or its 简体中文版. For interactive MCP App hosting, use the documented gateway host routes.

Security

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 serve

This command assumes the CLI is on your PATH; from a checkout, use dotnet run --project src/OpenClaw.Cli -c Release -- setup tailscale serve.

Docs

Browse AgentQi.dev or the complete repository documentation index.

Contributing

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.

License

MIT