~/cookiedclaw — claude code, in your pocket

install github ↗

ok plugin cookiedclaw@cookiedclaw-claude-code loaded            ··············  dev channel
ok mcp server telegram-channel on stdio        ··············  bun · 14 modules
ok grammy bot @cookiedclaw_bot polling           ··············  long-poll
ok tool-progress hook bound                      ··············  localhost:53117
i  paired users · 1                              ··············  you only
i  billing path · claude.ai max                  ··············  no extra api calls
 
$ waiting on telegram dm▌

OpenClaw, but Claude Code is the harness.

The harness you already have. Not another one.

A Telegram-resident agent that lives inside your Claude Code session over a custom MCP channel. Your tokens, your Max plan, your tools — now reachable from a chat thread.

// note from the author The other claws are gateways: your chat → their runtime → bring-your-own auth. cookiedclaw is a Claude Code plugin — it is the runtime. Same Max plan, same skills, same hooks. No second box to host.

$ install→ github ↗ scroll ↓

cookiedclaw — a chocolate-chip cookie with little orange claws

cookiedclaw
v0.1 · beta · apr 2026

02origin

what stops me from using claude code instead of openclaw? UX.
cookiedclaw is the UX layer.

timur, on a weekend

03 / harnesses 01 /12

ls /usr/local/bin/ | grep -i claw

▸OpenClaw

▸NanoClaw

▸NanoBot

▸ClaudeClaw

▸NemoClaw

▸IronClaw

▸ZeroClaw

▸profClaw

▸Hermes Agent

▸MoChat

▸AnyClaw

cookiedclaw

category: external gateway
runtime: standalone process
auth path: bring your own

terminated · ledger

01OpenClawexternal runtime
02NanoClawexternal runtime
03NanoBotexternal runtime
04ClaudeClawexternal runtime
05NemoClawexternal runtime
06IronClawexternal runtime
07ZeroClawexternal runtime
08profClawexternal runtime
09Hermes Agentexternal runtime
10MoChatexternal runtime
11AnyClawexternal runtime

terminated 00/11

Your VPS, texting you back.

Run Claude Code on a server, a home box, a forgotten mac mini — then drive it from the train, the kitchen, anywhere a Telegram thread reaches.

The agent is resident in the chat. Not polled, not relayed — there.

where the official telegram@claude-plugins-official plugin gives you a thread, cookiedclaw gives you a workspace — identity files, a setup wizard, an auto-mirrored slash menu, and live tool progress streaming back as it runs.

05ninety seconds

If you have Claude Code, you have this.

~/$ cookiedclaw setup

$ claude plugin marketplace add cookiedclaw/cookiedclaw-claude-code

$ claude plugin install cookiedclaw@cookiedclaw-claude-code

$ mkdir -p ~/cookiedclaw && cd ~/cookiedclaw

$ claude --dangerously-load-development-channels plugin:cookiedclaw@cookiedclaw-claude-code

> /cookiedclaw:setup

wizard runs · botfather token · you'll be texting your repo in ~90 seconds

then run /cookiedclaw:setup inside CC. or read the source — it's small.