---

name: CodexClaw description: Install and operate a Telegram bot that exposes Codex, MCP, GitHub subagents, repo switching, and minimal frontend dev-server control.

CodexClaw

What This Skill Does

• runs Codex through Telegram
• keeps coding sessions scoped to chat + repo
• exposes /repo, /status, /skill, /gh, /mcp, and /dev
• supports frontend repo debugging with /dev start|stop|status|logs|url

Install

git clone https://github.com/MackDing/CodexClaw.git
cd CodexClaw
npm install
cp .env.example .env

Required Env

Set at least:

BOT_TOKEN=123456789:telegram-token
ALLOWED_USER_IDS=123456789
STATE_FILE=.codex-telegram-claws-state.json
WORKSPACE_ROOT=.
CODEX_WORKDIR=.
CODEX_BACKEND=sdk

Start

npm run start

Verify

npm run check
npm run lint
npm run format:check
npm test
npm run healthcheck

Telegram Quick Use

/status
/repo
/skill
/repo my-project
/dev status
/gh create repo my-new-repo
/gh confirm

Frontend Debugging

Use these commands inside the current repo selected by /repo:

• /dev start
• /dev stop
• /dev status
• /dev logs
• /dev url
• /gh create repo ..., /gh push, and /gh commit "..." are explicit write paths
• /gh confirm executes the pending GitHub write action
• plain-text create repo, commit, and push requests are blocked and turned into guidance

Rules:

• dev script is preferred
• start script is used as fallback
• frontend runtime is shared per repo, not per chat
• /dev is not a general-purpose shell

Notes

• superpowers is an internal workflow and shows up in /status, not as a toggleable /skill
• /sh remains a restricted operator channel and is separate from /dev