| name | CodexClaw |
|---|---|
| description | Install and operate a Telegram bot that exposes Codex, MCP, GitHub subagents, repo switching, and minimal frontend dev-server control. |
- 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
git clone https://github.com/MackDing/CodexClaw.git
cd CodexClaw
npm install
cp .env.example .envSet at least:
BOT_TOKEN=123456789:telegram-token
ALLOWED_USER_IDS=123456789
STATE_FILE=.codex-telegram-claws-state.json
WORKSPACE_ROOT=.
CODEX_WORKDIR=.
CODEX_BACKEND=sdknpm run startnpm run check
npm run lint
npm run format:check
npm test
npm run healthcheck/status
/repo
/skill
/repo my-project
/dev status
/gh create repo my-new-repo
/gh confirm
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 confirmexecutes the pending GitHub write action- plain-text
create repo,commit, andpushrequests are blocked and turned into guidance
Rules:
devscript is preferredstartscript is used as fallback- frontend runtime is shared per repo, not per chat
/devis not a general-purpose shell
superpowersis an internal workflow and shows up in/status, not as a toggleable/skill/shremains a restricted operator channel and is separate from/dev