
DuDuClaw
io.github.zhixuli0406由 GitHub 帳號 zhixuli0406 發布v1.74.0更新於 Oct 24, 2026
Local persistent memory and Markdown wiki for AI coding agents: 24 MCP tools, no gateway required.
發布方自己的服務:claw.mobile AI tools catalogue
概覽
為 AI 程式開發代理提供本機持久記憶與 Markdown 知識庫,透過 stdio 提供大量 MCP 工具,不需閘道。
- 可以做什麼
- 在本機 SQLite 中儲存並檢索對話記憶與關鍵事實,支援事實時序鏈與遺忘曲線歸檔
- 讀寫共用的 Markdown 知識庫,並自動注入代理上下文
- 管理代理、技能與任務看板,包含排程派送任務
- 將工作路由到 Telegram、LINE、Discord、Slack 等訊息頻道
- 串接 Odoo ERP,存取 CRM、銷售、庫存與會計紀錄
- 透過 stdio 或帶 Bearer 驗證的 HTTP/SSE 傳輸使用同一套工具
- 適用情境
- 適合希望程式開發代理能跨工作階段、跨後端保留上下文,共用本機知識庫,並在單一本機服務中統籌任務與訊息頻道,而不必自行打造這層基礎設施的情況。
- 執行需求
- 以本機程序方式在使用者電腦上執行(僅桌面版),透過 npm 套件 duduclaw 安裝,npm 安裝需要 Node.js 20 以上。需要以 DUDUCLAW_MCP_API_KEY 環境變數提供獨立伺服器金鑰,可用 mcp init 指令產生。代理執行環境本身還需要一個 AI 後端(受支援的 CLI,或 OpenAI 相容的 API 金鑰或本機模型伺服器)。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 DuDuClaw,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
DuDuClaw
DuDuClaw turns AI command-line tools such as Claude Code and Codex into AI employees who actually deliver: they staff eleven messaging apps like Telegram, LINE, and Discord, an independent judge reviews their work before it ships, and every dollar they spend gets logged.
All you need is one Rust binary. Channel routing, conversation memory, multi-account rotation, behavioral guardrails, local inference, and a web dashboard are built in; swap the AI brain between ten CLI backends (Claude Code, Codex, Grok and others) or any OpenAI-compatible API whenever you like, and your config and memory stay on your own machine. The core is Apache 2.0.
[DuDuClaw v1.74.0 web dashboard, task board in list view: seven demo tasks grouped as To Do, In Progress, In Review, Done and Stuck, each with an ID, a tag such as support or marketing, and a priority]
The task board in the v1.74.0 dashboard. The staff and tasks are demo data.
[CI] [Version] [npm] [Glama MCP server score] [License: Apache-2.0]
Quick start (needs Node.js 20+; prefer a desktop app? see Install):
Table of contents
- Why DuDuClaw?
- Architecture at a glance
- Prerequisites
- Install
- Quick start
- Feature overview
- CLI commands
- Trust and security
- Comparison
- Documentation
- License
Why DuDuClaw?
If you run claude or gemini in a terminal now and then, the native CLIs are all you need. The moment you want an AI staffing your LINE official account, covering your team's Discord, or running several agents with different jobs, you end up building a whole infrastructure layer yourself. DuDuClaw ships that layer:
v1.76.0: scheduled assignments let you hand work to an AI employee for later or on a repeat, from chat or the dashboard. Each run checks the creator's current permission.
Architecture at a glance
The AI runtime is the brain, DuDuClaw is the plumbing, and MCP (JSON-RPC 2.0) is the bridge. Swap the brain, keep the plumbing:
The Rust workspace is 24 crates: the duduclaw-core foundation, the duduclaw-gateway service layer, the duduclaw-llm unified API layer, duduclaw-inference for local models, duduclaw-memory for cognitive memory, duduclaw-security, and more. Full design in ARCHITECTURE.md.
Experimental calibrated local routing uses Varun Kotte's UCCI (arXiv:2605.18796). See UCCI calibrated cascade for configuration and data preparation.
The same gateway + dashboard also ships as a whole machine: DuDuClaw OS is a Yocto-built appliance image. Its Yocto layer and release pipeline live in their own repo and vendor this repo's Rust workspace as a trimmed snapshot; see the Install section below.
Prerequisites
DuDuClaw doesn't ship its own LLM — you need an AI brain first. Pick one (you can also set this up later in the browser wizard):
- Install one of the supported AI CLIs, such as Claude Code or Codex (the full list is in multi-runtime); Gemini CLI is no longer a DuDuClaw runtime. Anthropic's policy does not permit third-party products to offer Claude.ai login, route requests through Free/Pro/Max plan credentials on their users' behalf, or store those credentials, and Anthropic may enforce this without notice (users have reported suspended accounts). An API key is the supported path; subscription sign-in stays available behind a risk notice you have to accept
- Bring an API key for any OpenAI-compatible provider
- Or run a local model behind an OpenAI-compatible server (llama-server, Ollama, vLLM, llamafile) — no cloud account needed
In the Dashboard, one-click login supports Claude, Codex, Grok, Kimi, Copilot, Kiro and OpenCode when the CLI is installed. Codex uses codex login --device-auth: open the verification page shown by the CLI, enter its device code, and wait for completion. The browser does not need access to a Docker callback port, and pasting a callback URL code into the Dashboard does not authenticate. On the Accounts page, the API Token card can delete a saved account after you confirm its account id; revoke the key separately at its provider if needed.
Install
Desktop app (recommended for personal use)
A native Tauri build that starts the local gateway automatically when you launch it — no terminal required — and shares ~/.duduclaw with the CLI. Download from Releases:
The macOS desktop build is available again from v1.68.1 (signed and notarized). v1.67.0 through v1.68.0 have no macOS build; Windows and Linux builds exist for those versions.
Open it and you're done — the in-app wizard walks you through picking an AI backend and creating your first agent, no commands needed.
npm (advanced / server use, all platforms including Windows)
For running on a server, scripting automation, or if you just prefer the command line. The only prerequisite is Node.js 20+:
This installs a prebuilt binary for your platform (macOS ARM64/x64, Linux x64/ARM64, Windows x64). No compiler, no Rust.
⚠️ If the install asks you for Rust / MSVC Build Tools and a 1.5-hour compile, you took a wrong turn. That path is "build from source" for contributors; regular users should use the npm command above.
DuDuClaw OS (appliance image, pre-GA)
If you would rather not dedicate a computer, get a box that runs the moment you plug it in: DuDuClaw OS is a Yocto-built Linux operating system in which the AI agent is a native resident: it boots into its own desktop (compositor / shell, lock screen, Cmd+K delegation bar), so a person and the AI share one x86-64 box without getting in each other's way — the agent's GUI work runs in a shadow workspace by default, and the moment you touch the keyboard or mouse, whatever it was driving on your desktop yields. The desktop edition ships with A/B atomic updates and rollback, a read-only root, and preloaded Chromium / LibreOffice (Steam installs from Flathub) plus a Chinese IME; Secure Boot signing, dm-verity and TPM2 are build-time overlay options that remain disabled as of the current v0.4.0 release, so boot with Secure Boot turned off in the BIOS/UEFI.
The current release is v0.4.0 (embedding platform v1.73.4). The gateway now runs as a non-root user with its containers on rootless Podman, SSH is off by default, and the base image gets the same firewall as the desktop edition. The upgrade is one-way: once v0.4.0 has booted successfully, a device cannot roll back to v0.3.0 or earlier, which stay on the Releases page only as older releases. Download the whole-disk .wic.zst (desktop edition), the installer-desktop installer .iso (writes the desktop edition), or the plain installer .iso (writes the base image, without the app layer) from DuDuClaw-OS Releases; every file comes with a .sha256 and a minisign signature, and the verification commands are on the OS README on the docs site. This is a bring-up line (0.x): QEMU-verified, not yet booted on real hardware, and upgrading an existing v0.3.0 box through the A/B update has not been verified yet. Hardware requirements and compatible machines: docs/guides/hardware-requirements.md; product overview: docs/features/50-duduclaw-os-appliance.md.
Build from source
Prerequisites: Rust 1.85+, Node.js 20+.
Python SDK (optional library)
The core gateway/CLI is a Rust binary and needs no Python. The duduclaw package on PyPI is a pure library for import duduclaw (agents / channels / mcp / memory_eval modules) with no command-line entry point, which is why pipx install duduclaw fails by design. If you need it:
Quick start
-
Desktop app: just open it — the gateway starts automatically and the wizard appears right inside the app.
-
npm / build from source:
Either way, the first visit takes you through a wizard: pick an AI backend, create your first agent, then chat with it in the built-in WebChat — no need to run duduclaw onboard from a terminal first. Later, paste a bot token on the Channels page to put the same agent on Telegram, LINE, Discord, and the rest, without restarting.
Useful next steps:
Feature overview
Full feature list in docs/features/feature-inventory.md; version history in CHANGELOG.md.
CLI commands
Run duduclaw --help for the full command list and subcommands; developer topics are in the development guide.
Trust and security
What you install is fully transparent:
- What's in the npm package: a small JS wrapper plus platform binaries (
@duduclaw/<platform>optionalDependencies).postinstallonly checks that the platform package is present (install.js); nothing is downloaded from arbitrary URLs or executed - No telemetry: no usage data or conversation content is sent to us. The gateway checks GitHub Releases for updates every 6 hours; with a paid license installed it also refreshes the license with the license server (every 3–7 days depending on tier) and fetches the revocation list daily. Without a license file there is no licensing traffic. Secrets stay on your machine, encrypted with AES-256-GCM
- No privilege escalation: runs entirely in user space
- Maintainer: Dudu Technology Ltd. (registered in Taiwan, tax ID 94139082)
- High-risk actions in chat: an employee asks for approval of a high-risk computer-use step in its channel, and you answer with the request's full ID. An operation whose result is unknown is never re-sent automatically; an Admin settles it in the dashboard. See the operator guide
- Browser login persistence (v1.76.0): optional encrypted per-employee container snapshots, default off, with reset and handover protection. Final container acceptance is pending. See the guide.
- Team browser viewing (v1.76.0): reporting-line managers can view masked snapshots and stop a subordinate’s human-started container session. Existing direct bindings retain their controls. Session-bound viewing links can return here after sign-in and appear in verified conversations or the matching task/run record. See the guide.
Every release asset ships with three kinds of verification: a SHA-256 checksum, a cosign keyless signature, and a minisign Ed25519 signature (the built-in auto-updater enforces this one and refuses unsigned or tampered releases):
Don't trust prebuilt binaries? Building from source takes three commands. Report vulnerabilities via SECURITY.md.
Why does a "new" package start at version 1.3x? DuDuClaw spent months in a private repo (400+ commits) before going public; the full history is in the git log.
Comparison
Documentation
Enterprise personal Google connections (v1.76.0): connect your own account, allow individual AI employees, and withdraw consent in My connections.
- Read-only team conversations: Enterprise dashboard and API (v1.76.0) for report WebChat and masked external conversations, with staff notices, an activation boundary and mandatory audit. Direct Viewer/Operator history now keeps own WebChat full, masks external conversations and hides other accounts; Owner/Admin remain full. This behavior change has an explicit migration setting.
- Self-service: Who viewed my conversations shows only your own team-history receipts (guide).
- ARCHITECTURE.md: full system architecture
- docs/README.md: public docs index (architecture / RFC / ADR / specs / guides)
- docs/guides/deployment-guide.md: production deployment (Tailscale / Docker / systemd / auto-update / monitoring)
- docs/guides/development-guide.md: dev environment and agent development
- MCP operation lifetimes: host API reference (v1.76.0) for per-operation HTTP authority
- docs/guides/custom-mcp-tool.md: writing custom MCP tools
- docs/spec: SOUL.md and CONTRACT.toml format specs
- docs/features/50-duduclaw-os-appliance.md: the DuDuClaw OS appliance; 52-desktop-edition.md: the desktop edition, one machine shared by a person and the AI; hardware requirements in hardware-requirements.md; app compatibility, image build and releases all live in the DuDuClaw-OS repo (see its
docs/guides/app-compat.md) - CHANGELOG.md: version history
License
Open core: the core is Apache License 2.0, free to use, modify, and distribute. Commercial add-ons (commercial/, not in this repository), such as the premium industry packs, are closed source and paid; a license key unlocks them. The license-verification client (crates/duduclaw-license) is part of the Apache 2.0 core. See LICENSING.md.
Commercial licenses, enterprise rollout, training and support are provided by our authorised distributor, Future Corp (未來企業股份有限公司). We do not sell directly.
Built with louis.li
來源:README.md,提交 feb7d22
工具
0版本歷史
3- v1.74.0最新Oct 16, 2026
- v1.73.4Oct 15, 2026
- v1.71.0Oct 7, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Claw 整合
claw.mobile AI tools catalogue
mobile.claw官方發布者
收錄 33 款 AI 應用程式建構工具與程式設計助理的唯讀目錄,讓助理查詢方案、價格、比較結果,並依需求媒合工具。
JustClaw-It
com.it.justclaw官方發布者
遠端 MCP 伺服器,讓程式開發助理搜尋經授權審查的程式元件庫、附上姓名標示取得原始碼,並查核授權與安全公告。

ClawGrab
com.getclawgrab
取得公開影片與播客連結的文字稿,並提供摘要、社群貼文、部落格草稿、金句與翻譯等 AI 文字工具。

ClawMaven
由 GitHub 帳號 foodyogi 發布
ClawMaven 是遠端 MCP 端點,為 AI 代理提供部署前治理:姿態評分、政策、預算上限檢查與信任清單。

ClawTank
由 GitHub 帳號 HMAKT99 發布
隨 macOS RDP 伺服器 ClawTank 提供的 MCP 伺服器,讓 Mac 上的 AI 代理截圖並操控桌面。