zeroclaw-labs/zeroclaw

Fast, small, and fully autonomous AI personal assistant infrastructure, any OS, any platform — deploy anywhere, swap anything 🦀

View on GitHub ↗Jump to charts ↓Open shareable report →

zeroclaw-labs/zeroclaw has 32k+ stars and 4.5k+ forks on GitHub, is written in Rust, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 1st, 2026
Created on February 13th, 2026
Open Issues & Pull Requests: 987 (+1)
GitHub issues: Enabled
Number of forks: 4,974
Total Stargazers: 32,983 (+0)
Total Subscribers: 83 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.2 hours
Mean response time: 3.9 days
90th percentile: 11.9 days
Tracked items: 3,177

Maintainer activity

26 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 4% of issues opened in the past year have never received a reply. 43% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Almost all tracked open issues have seen activity in the last three months. 82% of issues opened in the past year have been closed, leaving a working backlog. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 596
New in 7 days: 52
Closed in 7 days: 27
Avg open age: 42 days
Stale 30+ days: 269
Stale 90+ days: 1

Recent activity

Opened in 7 days: 51
Closed in 7 days: 23
Comments in 7 days: 43
Events in 7 days: 99

Top labels

  • bug (1,580)
  • status:accepted (1,136)
  • priority:p2 (1,121)
  • enhancement (1,073)
  • runtime (799)
  • risk:high (733)
  • status:no-stale (702)
  • status:in-progress (615)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ZeroClaw is an agent runtime that deploys as a single Rust binary to run autonomous AI assistants on your own machine.

The tool addresses the need for AI agents that operate under user control rather than through third-party services. It works by running locally on your hardware, connecting to LLM providers such as Anthropic, OpenAI, and Ollama, and exposing the agent through multiple communication channels including Discord, Telegram, Matrix, email, voice, and webhooks. The agent can act through tools like shell commands, browser automation, HTTP requests, hardware control, and custom MCP servers. All execution happens in your workspace with your API keys, keeping data and computation local.

ZeroClaw suits developers and users who want full ownership of their AI assistant infrastructure without relying on cloud-hosted agent platforms. It works across operating systems including Linux, macOS, Windows, FreeBSD, and NixOS, with Docker support available. The project emphasizes that you own the agent, the data, and the machine it runs on. Those evaluating adoption should note that the tool is built in Rust and distributed as a prebuilt binary for most platforms, with guided installers available for Unix and Windows to simplify setup.

The project maintains an active build pipeline with passing continuous integration checks. Documentation is comprehensive, including a philosophy section explaining the project's core opinions, architecture documentation, and platform-specific setup guides. The codebase includes translated documentation managed through git submodules, indicating sustained internationalization effort. Installation tooling is automated through cargo-based generation of platform-specific installers, and the project provides multiple installation paths to accommodate different user preferences and technical backgrounds.