Project-scoped workspace
Sessions, memory, skills, configuration, and tasks are organized around the real project folder.
Skip to content
Unified Session Core · .NET 10 · Agent Harness
Craft a persistent AI workspace around your project
DotCraft connects CLI, Desktop, IDEs, chat bots, APIs, and automations to one workspace so sessions, memory, skills, and tools stay coherent across every entry point.
One core, many entry points
DotCraft does not keep separate agent loops for each client. The Unified Session Core owns execution, state, approvals, and observability.
Unified session model
The Thread, Turn, and Item model is shared by CLI, Desktop, ACP, QQ, WeCom, and automations.
Observability and governance
Approvals, tool calls, traces, Dashboard, and sandbox isolation make agent workflows easier to inspect and control.
Desktop first
Manage sessions, diffs, plans, and automations visually
Desktop is the recommended first entry point. Start with download, workspace initialization, and model configuration, then enable TUI, AppServer, ACP, channels, or automations as needed.
Protocols and SDKs for integration
AppServer exposes DotCraft over JSON-RPC via stdio or WebSocket, so external clients, channel adapters, and SDKs can reuse the same runtime.
Automations
Put agent work into a task pipeline
Local tasks and Cron provide scheduling, thread binding, activity display, and retry behavior inside the workspace.
Start in three steps
For first-time use, start from Desktop. Once that works, the same workspace can connect terminal, editor, API, SDK, and automation entry points.
Download DesktopInstall a release build, or build from source and start Desktop.
Choose a project folderSelect a real project folder so configuration, sessions, and tasks stay with that project.
Configure a model and chatSet an OpenAI-compatible API key or CLIProxyAPI, then send your first repository-understanding request.