A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled jobs, and runs directly on Anthropic's Agents SDK
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 32%
Response Time: 2d
First Timer Success: 15%
nanocoai/nanoclaw has a recorded first-timer success rate of 14.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nanocoai/nanoclaw respond to incoming external pull requests in approximately 52.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.9 places nanocoai/nanoclaw in the A tier.
The external contributor pull request merge rate for nanocoai/nanoclaw is 32.3%, based on public PR activity from non-core contributors.
nanocoai/nanoclaw currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled jobs, and runs directly on Anthropic's Agents SDK
Balanced & professional review environment in nanocoai/nanoclaw. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/nanocoai/nanoclaw?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~34 hours (40% approval). Large PRs (>500 lines) take ~254 hours (15% approval). Keep your diff compact for rapid review.
Problem Currently there is no way for users to start a fresh conversation session from within the chat. The sessionId is always carried forward across container restarts, meaning the full conversation history accumulates indefinitely. This causes two issues: Token waste — every new task sends the entire previous conversation history to Claude, even when it's completely irrelevant Context pollution — stale context from a previous task can confuse the agent on a new unrelated task The only current workaround is to manually delete the session from the database or remove data/sessions/{group}/.claude/, which is not user-friendly. Proposed Solution Add a /new (or /reset) command that users can send in any group chat to clear the current session: Deletes the stored sessionId for that group from the database Next message starts a fresh Claude Agent SDK session with no prior context Non-main groups can only reset their own session; main group can reset any group's session Why This Matt
Nanoclaw is very susceptible to indirect prompt injection. For instance, see Suggest at least highlighting the risk that untrusted data can take control of Nanoclaw. Current security considerations goes into detail around sandboxing, but doesn't address the agent being easily hijacked by an attacker via indirect prompt injection. This means an attacker can take full control of the host, including exfiltrating information. Can also share the payload used, but didn't wanna share widely.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to nanocoai/nanoclaw, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of nanocoai/nanoclaw acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 32.3% were successfully merged into the primary branch.
nanocoai/nanoclaw has a recorded first-timer success rate of 14.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.9 places nanocoai/nanoclaw in the Welcoming tier.
The external pull request merge rate is 32.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nanocoai/nanoclaw currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nanocoai/nanoclaw are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.