Entry Points Overview
There's more than one way to open a DotCraft workspace. Whichever you choose, you're working with the same agent: it reads the same .craft/ and shares the same session core and long-term memory. The only thing that changes is the surface you talk to it through.
Surface Shapes
| Entry | Surface | Best for |
|---|---|---|
| Desktop | Graphical desktop app | First-time use / long-running collaboration / complex diffs & approvals |
| TUI | Rust-native terminal UI | Terminal-native, SSH remote, lightweight |
| IDE / Editor (ACP) | Inside JetBrains / Obsidian / Unity / etc. | Read unsaved buffers, run via editor-managed terminal |
| Channels / Bots | QQ / WeCom / Feishu / Telegram / WeChat | Group chats, knowledge bots, support bots |
Decision Matrix
| I want to… | Recommended |
|---|---|
| Start using DotCraft for the first time | Desktop |
| Work over SSH on a remote server | TUI or AppServer + remote TUI/Desktop |
| Let the IDE feed unsaved buffers to the agent | ACP |
| Bring an agent assistant into a Discord / QQ group | Channels |
| Share one workspace across multiple clients | AppServer Mode + any of the above |
| Build a bot or custom client | SDK overview + AppServer Protocol |
| Run scheduled / CI automations | Automations + any entry to handle approvals |
Cross-Entry Sharing Principles
- One AppServer per workspace: locally coordinated by Hub; you do not manage it by hand.
- Threads resume across entries: a Thread opened in Desktop can continue in TUI / ACP; approvals render natively per platform.
- Single source of truth for config: model, security, automations all in
.craft/config.jsonand~/.craft/config.json; every entry reads the same file. - Entry switches are independent: ACP, Dashboard, Automations, and external channels are enabled per workspace.
First-Time Picking
If you have not started yet:
- Follow Getting Started to install Desktop.
- Walk through "select workspace + configure a model + first chat" inside Desktop.
- Add a second entry (TUI / ACP / Channels) only when a real need shows up.
Related docs
- Unified Session Core — the Thread / Turn / Item model behind cross-entry sharing
- AppServer Mode — remote, multi-client, custom integrations
- Hub Local Coordination — why "open and it just works" works