clawd-on-desk

Clawd lives on your desktop and reacts to what your AI coding agent is doing — in real time. Start a long task, walk away, come back when the crab tells you it's done.

Thinking when you prompt, typing when tools run, grooving or juggling for subagents, reviewing permissions, celebrating when tasks complete, sleeping when you step away. Ships with three built-in themes: Clawd (pixel crab), Calico (三花猫), and Cloudling (云宝), with full support for custom themes and imported Codex Pet animation packs. An optional official theme, Hash Sage (哈希仙人), can be downloaded from Settings → Theme.

Supports Windows 11, macOS, and Ubuntu/Linux. Windows releases provide separate x64 and ARM64 installers. Source builds require Node.js. Works with Claude Code, Codex CLI, Copilot CLI, Gemini CLI, Antigravity CLI (agy), Cursor Agent, CodeBuddy, WorkBuddy, Grok Build, Kiro CLI, Kimi Code CLI (Kimi-CLI), Qwen Code, ZCode, CodeWhale, opencode, MiMo Code, Pi, OMP, OpenClaw, Hermes Agent, Qoder, QoderWork, QwenWork (千问办公), Reasonix CLI, DeepSeek Harness, and TraeCode (Trae CN).

Features

Multi-Agent Support

• Claude Code — full integration via command hooks + HTTP permission hooks
• Codex CLI — official hooks with JSONL fallback (~/.codex/sessions/), auto-synced by default with real permission bubbles
• Copilot CLI — optional command hooks via ~/.copilot/hooks/hooks.json (install from Settings → Agents; see the Copilot guide for manual JSON fallback)
• Gemini CLI — optional command hooks via ~/.gemini/settings.json (install from Settings → Agents or run npm run install:gemini-hooks)
• Antigravity CLI (agy) — optional command hooks via ~/.gemini/config/hooks.json (install from Settings → Agents or run npm run install:antigravity-hooks); state-only: Clawd never pops a permission bubble for agy. Every Allow / Deny / Always-allow choice happens in agy's own terminal menu
• Cursor Agent — optional Cursor IDE hooks in ~/.cursor/hooks.json (install from Settings → Agents or run npm run install:cursor-hooks)
• CodeBuddy — optional Claude Code-compatible command hooks + HTTP permission hooks via ~/.codebuddy/settings.json (install from Settings → Agents or run node hooks/codebuddy-install.js)
• Custom HTTP agents — register another local executable in Settings and POST lifecycle events to Clawd's dynamic /state endpoint. Registration does not install hooks or make an arbitrary application report automatically; v1 is state-only and leaves permission decisions in the application's own UI. See the custom HTTP agent guide.
• WorkBuddy — optional Claude Code-compatible command hooks via ~/.workbuddy-ai/settings.json (current) or ~/.workbuddy/settings.json (legacy; install from Settings → Agents or run node hooks/workbuddy-install.js). State + Notification only: the desktop app resolves permissions in its own native sandbox and GUI, so Clawd does not register a permission hook for it.
• Grok Build — optional Claude Code-compatible command hooks via ~/.grok/hooks/clawd-on-desk.json (install from Settings → Agents or run node hooks/grok-install.js). State + Notification only: Grok has no blocking PermissionRequest hook, so Allow/Deny stays in the Grok TUI.
• Kiro CLI — optional command hooks injected into custom agent configs under ~/.kiro/agents/, plus an auto-created clawd agent that is re-synced from Kiro's built-in kiro_default after you install the integration, so you can opt into hooks with minimal behavior drift via kiro-cli --agent clawd or /agent swap clawd. State hooks are verified on macOS and Windows.
• Kimi Code CLI (Kimi-CLI) — optional command hooks via ~/.kimi/config.toml ([[hooks]] entries) (install from Settings → Agents or run npm run install:kimi-hooks)
• Qwen Code — optional command hooks via ~/.qwen/settings.json (install from Settings → Agents or run npm run install:qwen-hooks); state tracking and Qwen PermissionRequest desktop approval bubbles are supported
• ZCode — optional state + blocking PermissionRequest hooks via ~/.zcode/cli/config.json → hooks.events.* (install from Settings → Agents or run npm run install:zcode-hooks); Clawd shows manual Allow/Deny bubbles while global and per-session permission automation stays deferred. Clawd preserves explicit global or per-hook enabled:false settings and will not register over a foreign PermissionRequest hook
• CodeWhale — optional state-only lifecycle hooks via ~/.codewhale/config.toml ([[hooks.hooks]] entries) (install from Settings → Agents or run npm run install:codewhale-hooks); Phase 1 drives idle, thinking, working, sleeping, error, attention, and sweeping animations only, without permission bubbles or subagent tracking
• Reasonix CLI — optional state-only command hooks via <Reasonix home>/settings.json (~/.reasonix/settings.json on macOS/Linux, %APPDATA%\reasonix\settings.json on Windows; install from Settings → Agents or run npm run install:reasonix-hooks); Phase 1 drives lifecycle, tool, notification, compaction, and subagent-stop animations while leaving permission decisions in Reasonix's own terminal flow
• opencode — optional plugin integration via the effective file under ~/.config/opencode/ (config.json → opencode.json → opencode.jsonc, later wins) (install from Settings → Agents or run node hooks/opencode-install.js); zero-latency event streaming and permission bubbles with Allow/Always/Deny. Child sessions spawned by the task tool are headless and do not participate in the visible multi-session animation fanout
• MiMo Code — optional plugin integration via the effective file under ~/.config/mimocode/ (config.json → mimocode.json → default mimocode.jsonc, later wins; install from Settings → Agents or run npm run install:mimocode-plugin); shares the same @mimo-ai/plugin SDK and permission behavior as opencode. Its task child sessions are likewise headless
• Pi — optional global extension via ~/.pi/agent/extensions/clawd-on-desk (install from Settings → Agents or run npm run install:pi-extension); state-only interactive lifecycle and tool activity updates while preserving Pi's default YOLO behavior
• OMP (oh-my-pi) — optional global extension via ~/.omp/agent/extensions/clawd-on-desk (install from Settings → Agents or run npm run install:omp-extension); state-only interactive lifecycle and tool activity updates. session_stop records a completion candidate, and the following terminal agent_end commits it only after OMP has confirmed that no extension requested a continuation, so the finish chime waits for the turn to settle. If the community bridge clawd-on-desk-omp.ts is already present, Clawd leaves it in place and skips its own install
• OpenClaw — optional state-only plugin integration via ~/.openclaw/openclaw.json (install from Settings → Agents or run npm run install:openclaw-plugin; OpenClaw also needs an initialized config); local openclaw tui --local sessions drive Clawd animations, without permission bubbles or terminal focus in Phase 1
• Hermes Agent — optional plugin integration via Hermes' managed plugin directory (install from Settings → Agents or run npm run install:hermes-plugin); state, sessions, SessionEnd, terminal focus, and supported permission bubbles are available; Settings → Remote SSH can deploy the same plugin to a Hermes install on a remote host
• Qoder — optional state-only command hooks via ~/.qoder/settings.json (install from Settings → Agents or run npm run install:qoder-hooks); Phase 1 drives Clawd animations only — Qoder permission prompts are observed as notifications, and every Allow / Deny choice stays in Qoder's own flow
• QoderWork — optional state-only command hooks via ~/.qoderwork/settings.json (install from Settings → Agents or run npm run install:qoderwork-hooks); Phase 1 drives Clawd animations and the Session HUD — QoderWork permission events are observed silently as part of the working flow, and every Allow / Deny choice stays in QoderWork's own flow
• QwenWork (千问办公) — optional hook-only, state-only command hooks via ~/.QwenWorkCN/settings.json (install from Settings → Agents or run npm run install:qwenwork-hooks, uninstall with npm run uninstall:qwenwork-hooks); macOS and Windows desktop only — qwenwork.cn/download has no Linux client, so there is no WSL pairing. Phase 1 drives Clawd animations and the Session HUD; PermissionRequest / PermissionDenied are observed only and mapped to working, the hook's stdout is always {}, and Clawd never produces an Allow / Deny — QwenWork's native permission flow stays the only decision maker. No startup recovery: the desktop process is long-lived and does not mean a turn is running
• DeepSeek Harness — experimental, web-profile-only integration through a Clawd-managed in-process DSH plugin. Public session events drive Clawd state with per-session ordering, and public blocking approval/request calls can show an Allow Once / Deny bubble; no-decision always returns to DSH's native web answerer. ask_user_question stays entirely native to DSH, and Clawd never reads DSH projection storage. See the DeepSeek Harness guide