One personal AI agent. Any messenger. Any coding-agent runtime.

A self-hosted personal AI agent platform with two halves:

• 🪺 The gateway (cookiedclaw, in development) — long-running process that owns messenger polling, paired-user state, persistent identity, and exposes an MCP-over-HTTP contract. Always-on, runtime-agnostic.
• 🔌 Per-runtime adapters — thin plugins that wire a specific coding-agent runtime (Claude Code, Codex, Cursor, OpenCode) into the gateway. Each adapter knows its host's hooks/permissions deeply and stays maintained as that runtime evolves.

Cookie (the agent persona, the cookie 🍪 you DM) lives inside the runtime adapter, not the gateway — so identity, conversation, skills are runtime-native. The gateway is invisible plumbing: it gets your message off Telegram and into whichever runtime is healthy right now.

Existing personal-AI-agent platforms (OpenClaw, Hermes Agent, ZeroClaw, NemoClaw, …) all bundle a custom runtime + their own protocol layer. Switching coding-agent backends means re-learning the platform.

cookiedclaw splits the concerns. The runtime stays your runtime — your Claude Code license, your Codex setup, your Cursor — and the gateway is a thin transport that routes between any messenger and any MCP-speaking agent. Adapters are small (a few config files + skills), so a new runtime ships in days, not weeks.

The Anthropic-official telegram@claude-plugins-official plugin is a minimal baseline by design — PRs adding live progress, permission UX, daemon transport get closed without merge. cookiedclaw lives in the gap that creates: rich UX tier, written as a first-party plugin per runtime so it inherits skills, MCP, hooks, and sub-agents natively.

• Not a coding-agent rewrite. Your runtime is your runtime — we don't ship a Claude Code clone or a Codex shim. Adapters use the official runtimes.
• Not a billing trick. Use your existing Claude Max / Codex subscription / Cursor seat. No extra-usage opt-in, no API-key arbitrage, no run-charge per message.
• Not single-platform. Telegram first, but the gateway's transport layer is pluggable — Discord, Slack, iMessage, Signal, email follow.

The CC adapter is the only piece shipping today. Gateway is in development; for now CC handles messenger polling itself via the same plugin (will move into the gateway when it's ready).

claude plugin marketplace add cookiedclaw/cookiedclaw-claude-code
claude plugin install cookiedclaw@cookiedclaw-claude-code
mkdir -p ~/cookiedclaw && cd ~/cookiedclaw
claude --enable-auto-mode --dangerously-load-development-channels plugin:cookiedclaw@cookiedclaw-claude-code
# then inside CC:
/cookiedclaw:setup

Full quickstart in the adapter README.

_{made in Bishkek · MIT · 🍪}