CodexClaw
A thin orchestration layer on top of codex app-server that lets me control Codex through Telegram or iMessage while keeping my existing setup: skills, model defaults, workspace access, and approvals.
Why I Built It
Like many of you, I found OpenClaw fascinating. But I already had a Codex setup with a good amount of my own skills and agent customization, so I did not want to rebuild that part.
I really just wanted a way to talk to Codex at home so it could help me with things, and so I could use it to code things up when I needed to. CodexClaw is a thin gateway layer that lets you use messenger apps to talk to Codex. Right now that means Telegram, iMessage, permission controls, approvals, and the rest of the practical wiring.
Setup
It works with Telegram and iMessage via BlueBubbles, maps each external chat to a Codex thread with serialized turns, defaults to narrow allowlists and private owner approvals, and exposes a local control page at http://127.0.0.1:4188.