CodexClaw

Overview

CodexClaw is a sophisticated Telegram bot that connects to Codex through Node.js runtime with two backends: the Codex SDK and the legacy CLI/PTy path. It features task routing to the right execution surface, explicit tool handling through subagents, proactive automation via cron scheduler, and strict access controls with whitelist-only users. The bot separates Codex MCP responsibilities from Bot MCP responsibilities to avoid duplicate calls and extra latency. It supports interactive sessions scoped to chat + repo, manages bot-side MCP and GitHub subagents, and offers repository switching, status monitoring, and minimal frontend dev-server control directly from Telegram.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• /mcp list

  List available MCP servers

  Try:Show me all MCP serversTry:List MCP servers
• /mcp status

  Check MCP server status

  Try:What's the status of MCP serverTry:Check MCP server status
• /mcp reconnect

  Reconnect to an MCP server

  Try:Reconnect to MCP serverTry:Reconnect to my MCP server
• /mcp enable

  Enable an MCP server

  Try:Enable MCP serverTry:Turn on MCP server
• /mcp disable

  Disable an MCP server

  Try:Disable MCP serverTry:Turn off MCP server
• /mcp tools

  List tools available from an MCP server

  Try:Show me MCP toolsTry:List tools from MCP server
• /mcp call

  Call a tool from an MCP server

  Try:Use MCP tool toTry:Call MCP tool
• /gh commit

  Create a git commit

  Try:Commit changes with messageTry:Create a git commit
• /gh push

  Push git commits to GitHub

  Try:Push commits to GitHubTry:Push code to repo
• /gh create repo

  Create a new GitHub repository

  Try:Create new GitHub repoTry:Make a new repository on GitHub
• /gh run tests

  Run tests in GitHub

  Try:Run tests on GitHubTry:Execute tests in GitHub Actions
• /gh test status

  Check the status of a test job

  Try:Check test job statusTry:Get test status from GitHub

Comparable tools

Installation

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

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

# Start the bot
npm run start

FAQ

What is the difference between SDK and CLI backends?

The SDK backend uses Codex SDK threads and is preferred for new installs. The CLI backend uses PTy sessions and falls back to codex exec if node-pty cannot spawn on the host system.

How does MCP routing work in this bot?

Coding requests go directly to Codex (which can use its own MCP stack), while bot-side MCP is only used for explicit '/mcp' commands to avoid duplicate queries and extra latency.

Compare CodexClaw with