# ClawCode

> Persistent agents for Claude Code as a plugin, not a harness. Memory, personality, messaging across WhatsApp, Telegram, and Discord, plus a service mode for 24/7 runs. Imports from OpenClaw.

- **URL**: https://www.freshcrate.ai/projects/ClawCode
- **Author**: crisandrews
- **Category**: MCP Servers
- **Latest version**: `v1.7.4` (2026-05-31)
- **License**: MIT
- **Source**: https://github.com/crisandrews/ClawCode
- **Language**: TypeScript
- **GitHub**: 49 stars, 10 forks
- **Registry**: github (`crisandrews/ClawCode`)
- **Tags**: `ai-agent`, `autonomous-agent`, `claude`, `claude-code`, `claude-code-plugin`, `dreaming`, `mcp`, `memory`, `typescript`

## Description

Persistent agents for Claude Code as a plugin, not a harness. Memory, personality, messaging across WhatsApp, Telegram, and Discord, plus a service mode for 24/7 runs. Imports from OpenClaw.

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `v1.7.4` | 2026-05-31 | High | ### Fixed - **`/agent:channels` now surfaces a locked-out WhatsApp server instead of reporting it as fine.** The channel detector previously only checked that `status.json` *existed*; it never read the live `status`. So when a second session held the WhatsApp single-device lock (common after an in-session update/reload, or when a background/service/scheduled session was still alive), `/agent:channels` showed `active: ❓` and the agent stayed silent while the user saw "typing…" on their phone but |
| `v1.7.1` | 2026-05-19 | High | ClawCode 1.6.0's always-on protected-paths defense refuses MCP `Write` to `agent-config.json` and channel `access.json` regardless of mode — by design for security, but two legitimate setup flows broke as a side effect. The first-run bootstrap wizard (every new user) couldn't write its own `agent-config.json`, and `/whatsapp:access pair <code>` couldn't write `access.json` when the channel state-dir resolves to the global fallback `~/.claude/channels/whatsapp/`. Both flows now route the file wri |
| `v1.5.0` | 2026-05-14 | High | ## What this release brings  ClawCode 1.5.0 ships a brand-new **opt-in privacy layer** for indexed messaging-channel content. Until now, when your agent paired with `claude-whatsapp` and you ran `memory_search` or recalled context from dreams, the agent could see snippets from *every* chat it had indexed — regardless of the per-chat access rules `claude-whatsapp` already enforced on its own tools. This release closes that gap.  Turn it on with `/agent:scope wizard` and the wizard walks you throu |
| `v1.4.14` | 2026-04-21 | High | ### Changes  - Docs/wsl2: publish `docs/wsl2.md` walking Windows users from zero to a running agent via WSL2. Opens with a "where is your Claude Code running right now?" diagnostic (`uname -a` tells them whether they're already inside WSL2 or stuck on native Windows), so a Windows user with an existing native Claude Code install doesn't silently install ClawCode into an environment where the Linux code paths can't run. Then PowerShell `wsl --install`, Ubuntu deps (`nodejs npm jq git`), a separat |
| `v1.4.13` | 2026-04-20 | High | ### Changes  - Hooks/reconcile: emit a 4-line session banner at the top of every SessionStart — `=== CLAWCODE v<version> · MIT License ===`, docs/config link to the repo, an `/agent:doctor` tip, and a neutral issues/feedback invite. Version is read at runtime from `plugin.json` (jq with a `sed` fallback for jq-missing environments), so it never drifts from the manifest. Additive only: identity injection, the cron reconcile envelope, the `BOOTSTRAP.md` early-exit, and the jq-missing degraded path |
| `v1.4.12` | 2026-04-20 | High | ### Fixes  - Docs/readme: add a Troubleshooting bullet for the "my agent went silent for minutes after `/plugin update clawcode@agent`" case — it's the download running in the background with no progress indicator, not a hang. Tip: `/plugins-reload` afterwards to make the running session pick up the new cache cleanly before the next turn. Surfaced live after v1.4.11 shipped.  - Skills/about: reorder the Format-per-surface section so the tail-line language rule is the first thing an agent reads, |
| `v1.4.11` | 2026-04-20 | High | ### Fixes  - Skills/crons: `writeback.sh upsert` refuses (exit 5) when an active entry with the same `cron`+`prompt` already exists under a different key. Kills the "hook captured the CronCreate as `harness-<id>`, agent also ran a manual `upsert` with a custom key" duplicate pattern that silently produced double-firing reminders — observed earlier today on a live WhatsApp agent. `openclaw-import` is exempt; tombstoned entries are ignored.  - Hooks/cron-pretool: new `PreToolUse` hook that gates ` |
| `v1.4.9` | 2026-04-19 | High | ### Fixes  - Skills/release: removed `skills/release/` from the plugin distribution. It was added at plugin scope in v1.4.7-v1.4.8 by mistake — every end user of an agent (Cloudy, Wally, etc.) saw a "release" skill in their `/plugin` viewer that had nothing to do with their agent's workspace. The release flow is a maintainer-only tool and now lives at user-scope on the maintainer's own machine, not in the published plugin. Plugin manifest, end-user agent config, and runtime behavior are unchange |
| `v1.4.8` | 2026-04-19 | High | ### Changes  - Skills/release: adopt the release-notes format used by `openclaw/openclaw` (~360k stars) as the canonical style for ClawCode CHANGELOG entries and `gh release` bodies. Two groups only (`### Changes` / `### Fixes`), bullets prefixed with `Area/subarea:` scope, one-line narrative + outcome, optional `(#PR) Thanks @user.` suffix, link back to CHANGELOG at the end. Mirrors what readers already see on OpenClaw's releases page so the style is familiar across both projects. Concrete work |
| `v1.4.7` | 2026-04-19 | High | ### Added  - **`/about` and `/version` slash commands** for the agent. Surfaces a 3-line card with the plugin name, current version, and the repo URL — so users who installed via marketplace can find docs / file issues / star the project right from inside their agent on any channel (CLI, WhatsApp, Telegram, Discord, iMessage). Version is read dynamically from `plugin.json` so it never goes stale. - **`skills/release/` — the release flow as an actual skill** (not just a memory). Codifies the 4 ma |

## Dependency audit

- **Score**: 100/100
- **Total deps**: 5
- **Resolved**: 5
- **Unresolved**: 0
- **License conflicts**: 0
- **Warnings**: 0
- **Scanned**: 2026-04-27

## Citation

- HTML: https://www.freshcrate.ai/projects/ClawCode
- Markdown: https://www.freshcrate.ai/projects/ClawCode.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/ClawCode/deps

_Generated by freshcrate.ai. Indexes github releases for AI-agent ecosystem packages._