Download the desktop app from GitHub Releases:

1. Install the .NET 10 SDK
2. Install the Rust toolchain
3. Install Node.js
4. Run build.bat
5. Run build/release/DotCraft-Desktop-Setup.exe

On first launch, choose a folder as your workspace and follow the setup wizard to initialize it.

DotCraft currently supports two setup paths:

• An OpenAI-compatible API key, such as the official API or providers like OpenRouter
• A Coding Agent CLI reverse proxy based on CLIProxyAPI

For the full configuration surface, see the Configuration Guide.

For the recommended visual setup flow in the built-in Dashboard, see the Dashboard Guide.

DotCraft organizes its entry points around the Unified Session Core: CLI, Desktop, IDEs, bots, and automations do not each maintain their own agent loop, but reuse the same execution engine and session model.

Here is how that differs from a traditional gateway-style architecture:

You can choose the entry point that best fits your workflow:

CLI	TUI
Desktop	ACP

CLI is the most direct entry point for working with DotCraft in a local project directory. It is also the default starting point for understanding the overall workflow before expanding into AppServer, Desktop, or automation scenarios.

TUI is for users who want a richer terminal experience. It is built on Ratatui, connects to AppServer over the Wire Protocol, and reuses the same session capabilities.

AppServer is DotCraft's unified backend boundary for exposing capabilities over a JSON-RPC Wire Protocol via stdio or WebSocket. It is the right entry point for remote CLI, multi-client access, and custom integrations in any language. See the AppServer Guide.

Desktop is for users who want a graphical workspace for conversations, diffs, plans, and automation review. It acts as a graphical AppServer client and consumes the same session, approval, and automation capabilities over the Wire Protocol. See the Desktop Client README for details.

Editors and ACP are for users who want DotCraft embedded directly into development tools, including Unity, Obsidian, and JetBrains IDEs. The key idea is not a separate editor-only agent, but an ACP bridge that connects the editor to the same AppServer runtime. Start with the ACP Mode Guide; for Unity specifically, see the Unity Integration Guide and the Unity Client README.

QQ / WeCom are DotCraft's native social channels and require no extra dependencies. For setup details, see the QQ Bot Guide and WeCom Guide.

For more social channels, DotCraft integrates through SDK-based extensions. See the Python SDK and TypeScript SDK.

DotCraft currently includes integrations for Telegram, WeChat, and Feishu/Lark.

Telegram (Python SDK)	WeChat (TypeScript SDK)

Automations are for running local tasks and GitHub-driven workflows. See the Automations Guide.

Desktop Automations	GitHub tracker
View automated tasks in the desktop application.	Automatic PR reviews.

Dashboard is DotCraft's visual inspection and configuration surface for sessions, traces, and workspace settings. See the Dashboard Guide for details.

Usage overview	Session trace
Usage and session statistics, aggregated by channel.	Complete record of tool calls and session history.

Sandbox Isolation is for scenarios where Shell and File tools should run inside a controlled execution boundary with stronger host isolation. Installation, configuration, and security details are covered in the Configuration Guide.

I want to use DotCraft directly in a repo

• Configuration Guide: configuration, tools, security, approvals, MCP, sandbox, startup modes, Gateway
• Dashboard Guide: Dashboard pages, debugging, and visual configuration
• Automations Guide: local tasks and GitHub issue/PR orchestration, agent dispatch, and human review flow
• Rust TUI Guide: build, launch modes, key bindings, slash commands, and theme configuration

I want to connect DotCraft to an editor or client

• Desktop Client Guide: Electron desktop application, build, launch, and feature overview
• ACP Mode Guide: editor/IDE integration (JetBrains, Obsidian, and more)
• Unity Integration Guide: Unity Editor extension and AI-powered scene and asset tools

I want to use DotCraft as a server or backend

• AppServer Guide: wire protocol server, WebSocket transport, remote CLI

I want to build bots, adapters, or extensions

• QQ Bot Guide: NapCat, permissions, and approvals
• WeCom Guide: WeCom push notifications and bot mode
• Python SDK: build external adapters with dotcraft-wire and the Telegram reference example
• TypeScript SDK: build external adapters with dotcraft-wire for WeChat, Feishu, and similar channels
• Hooks Guide: lifecycle hooks, shell extensions, and security guards

I want to continue into the full documentation set

• Documentation Index: full documentation navigation

We welcome code, documentation, and integration contributions. Start with CONTRIBUTING.md.

Inspired by nanobot and codex, and built on Agent Framework.

• HKUDS/nanobot
• openai/codex
• microsoft/agent-framework
• alibaba/OpenSandbox
• modelcontextprotocol/csharp-sdk
• openai/symphony
• router-for-me/CLIProxyAPI

Apache License 2.0