CodexClaw

Orchestrate secure Telegram-to-Codex coding sessions scoped by chat and repository.

34|16|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/MackDing/CodexClaw --skill codexclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CodexClaw
Source: https://github.com/MackDing/CodexClaw/tree/main
Command: npx skills add https://github.com/MackDing/CodexClaw --skill codexclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodexClaw solves the problem of safely operating OpenAI Codex from a Telegram chat while keeping execution organized per repository and enabling controlled tool and workflow routing.

Core Features & Use Cases

  • Zero-trust Telegram access: whitelist-only operators using ALLOWED_USER_IDS and secure runtime state persisted in STATE_FILE.
  • Codex coding execution with project scoping: maintains resumable coding sessions per chat + repo and supports /new, /exec, /auto, and /plan.
  • Bot-side control-plane subagents: explicit /mcp ... and /gh ... commands route to MCP server tooling and GitHub automation with confirmations for high-risk writes.
  • Frontend dev-server management: repo-scoped /dev start|stop|status|logs|url to help with iterative development without exposing general shell access.

Quick Start

Clone the repository, install dependencies, copy .env.example to .env, set BOT_TOKEN and ALLOWED_USER_IDS, then start the bot with npm run start.

Frequently Asked Questions about CodexClaw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run OpenAI Codex securely from a Telegram chat?

Run OpenAI Codex securely from Telegram by using a whitelist-only runtime that scopes coding sessions by chat and repository, persisting state to a file and streaming output safely. It requires a pinned entrypoint and whitelist access to operate.

Can I manage a frontend dev server through Telegram without exposing shell access?

Yes, you can manage a frontend dev server through Telegram using repo-scoped commands to start, stop, check status, and view logs. This allows iterative development management without exposing general shell access to the operator.

How do I route MCP server tooling and GitHub automation in a Telegram coding session?

Route MCP server tooling and GitHub automation in a Telegram coding session by using explicit slash commands. High-risk GitHub writes require confirmations, ensuring controlled automation within the same chat workflow.

Does the Telegram Codex runtime support planning-only runs and session persistence?

Yes, the Telegram Codex runtime supports planning-only runs and session persistence. It maintains resumable coding sessions per chat and repository, enabling per-project session restore for interactive coding workflows.

What do I need to set up before starting the Telegram Codex bot?

To set up the Telegram Codex bot, clone the repository, install dependencies, and configure environment variables including the bot token and allowed user IDs. This configuration enforces zero-trust access before starting the bot.