📦 Releases · 💬 Discussions · 🐛 Issues · 📘 Ask DeepWiki · Discord | English · 中文 · 日本語
Quick Start
CLI + Web Console (recommended)
npm i -g clawmaster
clawmaster # start the web console
Open http://localhost:16223 — the setup wizard walks you through OpenClaw engine detection and LLM provider configuration. No config files to edit.
clawmaster serve --daemon # run in background
clawmaster stop # stop the service
clawmaster doctor # verify your environment
[!NOTE] The current release is v0.3.0. Install with
npm i -g clawmaster.
Desktop App (Beta)
Download the installer for your platform from GitHub Releases:
| Platform | Format |
|---|---|
| macOS Apple Silicon | .dmg |
| macOS Intel | .dmg |
| Windows x64 | .msi, .exe |
| Linux x64 | .deb, .AppImage |
[!WARNING] Desktop builds are in beta. The CLI + Web Console is the recommended and most thoroughly tested install method.
From source
git clone https://github.com/openmaster-ai/clawmaster.git
cd clawmaster
npm install
npm run dev:web # web console + backend
npm run tauri:dev # desktop app
Requires Node.js 20+. Tauri desktop builds also need Rust — see tauri.app/start/prerequisites.
After Launch
- Pick an existing OpenClaw profile or create a new one.
- Connect at least one model provider and set a default model.
- Add channels, plugins, skills, or MCP servers as needed.
- Enable gateway or observability when you need runtime inspection.
Why ClawMaster
Most OpenClaw tooling stops at configuration. ClawMaster is your OpenClaw companion for real life — it goes beyond setup to help normal, non-technical users actually make practical use of OpenClaw as a digital personal assistant.
That means ClawMaster is not only for:
- editing config safely,
- connecting models and channels,
- monitoring runtime health,
but also for:
- making setup approachable,
- turning advanced agent capability into guided workflows,
- and gradually adding more guided learning and workflow support for real daily work and life goals.
Positioning: ClawMaster is the bridge between OpenClaw's power and everyday usability.
ClawMaster vs. CLI Only
| OpenClaw CLI alone | ClawMaster | |
|---|---|---|
| Initial setup | Hand-edit ~/.openclaw/openclaw.json | Guided wizard |
| Provider & model config | Edit JSON, restart | Form UI with live validation |
| Channel setup | Read docs, edit config | Step-by-step guides per platform |
| Observability | Mostly CLI and logs | ClawProbe-backed dashboard and runtime views |
| Memory management | powermem CLI | Management UI |
| Daily-use enablement | Mostly DIY | Product UX that is moving toward more guided use |
| Multiple profiles | Manual file juggling | Profile switcher |
| Desktop app | No | Yes — ships as .dmg / .msi / .AppImage |
| Self-hosted web console | No | Yes — Express, runs anywhere Node.js runs |
Who It Is For
"I want OpenClaw to be useful in my real life, not just correctly configured."
ClawMaster is designed to reduce the gap between installation and actual outcomes.
"I'm non-technical, but I still want a powerful AI personal assistant."
The product is moving toward guided setup, guided usage, and outcome-oriented learning instead of assuming comfort with JSON, terminals, or infra concepts.
"I manage OpenClaw for my team or family."
One place to configure channels, inspect runtime state, and make the stack easier for others to adopt.
"I'm building advanced agent workflows."
You still get provider management, observability, memory tooling, sessions, plugins, skills, and MCP in one place.
What You Can Do Today
- Setup and profiles — Detect OpenClaw, install missing pieces, create or switch profiles, bootstrap a local environment.
- Models and providers — Configure OpenAI-compatible and provider-specific endpoints, validate API keys, set runtime defaults.
- Gateway and channels — Bring up the gateway, follow guided setup for Feishu, WeChat, Discord, Slack, Telegram, and WhatsApp.
- Plugins, skills, and MCP — Enable or disable capabilities, install curated items, add MCP servers, import MCP definitions.
- Sessions, memory, and observability — Inspect sessions, manage memory backends, track token usage and estimated spend.
Product Tour
 Setup wizard · 2-step guided install, tiered providers |
 Overview · Runtime health, next-step task flows |
 Models · Multi-provider config with live key validation |
 Channels · Guided onboarding for 6 messaging platforms |
 Observe · ClawProbe-backed cost, tokens, session health |
 Memory · PowerMem-backed knowledge workspace |
 MCP · Servers, endpoints, and skill definitions |
 Skills · ClawHub marketplace with install and audit |
Roadmap
Six core capabilities — each moves from infrastructure toward real daily use:
| # | Capability | Status | What's here | What's next |
|---|---|---|---|---|
| 1 | Setup | Available | Guided wizard, 6+ LLM providers with key validation, 6 channel types (Feishu / WeChat / Discord / Slack / Telegram / WhatsApp), profile switching | One-click environment migration (#1), Windows + WSL2 first-class support |
| 2 | Observe | Available | ClawProbe-backed dashboard, per-session cost and token tracking, gateway health monitoring | Historical spend analytics, anomaly alerts, multi-profile comparison |
| 3 | Save | In progress | PowerMem UI with FTS5 local search, memory workspace management, graceful fallback to markdown grep | Full seekdb vector retrieval (#12), LLM Wiki — persistent knowledge base that compounds over time (#49) |
| 4 | Apply | In progress | PaddleOCR pipeline (upload → parse → structured markdown), layout-aware extraction | Photo → flashcard automation, invoice extraction templates, more scenario-first guided workflows |
| 5 | Build | Planned | Plugin/skill install and toggle, MCP server management, skill security auditing | Visual agent composer for skill chaining, LangChain Deep Agents integration, conversational agent builder |
| 6 | Guard | Planned | Skill Guard security scanning (dimension/severity/risk scoring), basic capability gating | API key vault (encrypted at rest), per-profile spend caps, RBAC for team deployments |
Browse label:roadmap to pick up an item. Leave a comment before starting so work does not overlap.
Versioning
ClawMaster follows Pride Versioning — PROUD.DEFAULT.SHAME:
| Segment | When to bump |
|---|---|
| Proud | A release you are genuinely proud of |
| Default | Normal, solid releases |
| Shame | Fixing something too embarrassing to talk about |
Pre-release tags (-rc.N) are used for release candidates.
📰 News
- 2026-04-25 🚀 v0.3.0 — first official release. Setup wizard, PaddleOCR, ERNIE image, cost observability, cron management, bundled skills refresh, and managed PowerMem support. CLI is the recommended install method; desktop builds remain beta.
- 2026-04-17 ✨ Brand and positioning launch — ClawMaster is now an OpenClaw companion for real life, not just a control plane. New wordmark, Apache 2.0 license, Pride Versioning.
Development
npm install
npm run dev:web # frontend + backend
npm run dev # frontend only (port 16223)
npm run dev:backend # backend only (port 16224)
npm run tauri:dev # desktop app
Testing and CI
npm test # unit tests (Vitest)
npm run build # type check + production build
npm run test:desktop # desktop smoke (macOS: real Tauri build; Linux/Win: WebDriver)
[!TIP] Run
npm test && npm run buildbefore opening a PR — the same steps run in CI.
CI covers core checks including TypeScript, unit tests, and desktop/web build validation.
Project layout
clawmaster/
├── packages/web/ React + Vite frontend
├── packages/backend/ Express backend for web mode
├── src-tauri/ Tauri desktop host
├── tests/ui/ YAML-based manual UI flow specs
└── bin/clawmaster.mjs CLI entry point
Runtime model: Desktop uses Tauri commands; Web mode talks to an Express backend over /api.
Contributing
We warmly welcome more contributions from builders, designers, technical writers, testers, and OpenClaw power users.
If you want to help ClawMaster become more useful for everyday users, please jump in — bug fixes, UX polish, docs improvements, onboarding flows, and future Master Class ideas are all valuable.
Start here:
- AGENTS.md — agent-friendly contributor rules
- CONTRIBUTING.md — setup, testing, commit, and PR guidance
- Ask DeepWiki — explore the repo before changing code
[!IMPORTANT] Run
npm testlocally before opening a PR. Please do not commit generated files or test logs. Node.js is the only permitted runtime — no new language dependencies.
Community: GitHub Discussions · Discord · Feishu