使用 Homebrew 安装 zeptoclaw

项目链接

• 主页
• 仓库
• 上游文档
• 软件包管理器页面

命令和别名

• zeptoclaw

项目历史

The public README frames ZeptoClaw as a response to several related assistant projects: OpenClaw for integrations, NanoClaw for small-container simplicity, NemoClaw for managed guardrails, and PicoClaw for edge efficiency. Its stated design center is a small Rust binary that keeps provider, tool, memory, channel, and safety features in one deployable unit.

The project is young and its public historical record is mostly its own documentation and comparison pages, so the safe history is architectural rather than social: it belongs to the 2026 wave of lightweight local/edge AI-agent runtimes trying to reduce the footprint and operational complexity of earlier assistant stacks.

采用历史

Adoption evidence is limited but concrete: the official docs document installation by script, Homebrew tap, Cargo from the Git repository, Docker image, and prebuilt binaries. The supplied package data lists Homebrew packaging, which makes it visible to macOS/Linux users experimenting with agent runtimes from the command line.

使用方式

Common usage starts with `zeptoclaw onboard`, then `zeptoclaw agent` for local agent prompts, `zeptoclaw batch` for prompt batches, and `zeptoclaw gateway` for running channel/webhook style service modes. The README also documents migration from OpenClaw-style installations into `~/.zeptoclaw` state.

为什么软件包爱好者会关心

ZeptoClaw matters to package nerds mainly as an example of the new AI-agent CLI packaging problem: the binary is small, but the runtime has to coordinate secrets, provider configuration, sandbox choices, channel gateways, and local state under a user config directory.

Because the project is young and self-described, package history should be read cautiously. The useful package-level facts are the single-binary distribution model, Homebrew/Cargo/Docker install paths, and the explicit focus on safety controls around autonomous tool use.

时间线

• 2026: ZeptoClaw documentation and comparison pages position it among OpenClaw, PicoClaw, NanoClaw, and ZeroClaw-style self-hosted AI assistant runtimes.
• 2026: Official docs describe installation through Homebrew tap, Cargo, Docker, and prebuilt binaries.

Related projects

• OpenClaw is cited by ZeptoClaw as the broad integration-heavy assistant it learned from.
• NanoClaw, NemoClaw, PicoClaw, and ZeroClaw are named by ZeptoClaw as adjacent assistant/runtime designs with different size, security, and integration tradeoffs.

来源

• https://github.com/qhkm/zeptoclaw#readme
• https://github.com/qhkm/zeptoclaw/blob/main/docs/COMPARISON.md
• https://zeptoclaw.com/docs/
• https://zeptoclaw.com/docs/getting-started/installation/
• source_facts.package-manager