Add Codex to your Poke.
Setup is intentionally easy: two steps, one Poke recipe, and Codex works in the projects you allow.
Run Codex, anywhere. Powered by your Poke.
Keep the bridge running and Codex answers wherever your Poke lives — phone, watch, iMessage, WhatsApp. Ask for a review, a fix, or a diff, and the work lands in a local workspace you allowed.
project and tell me what it does.
poke ▸ using the Pokedex recipe…
you ▸ Now review the code and flag bugs
or risks.
poke ▸ calling pokedex_review with read_only sandbox…
▸ agent workspace pokedex · alias resolved
▸ agent sandbox read_only · policy ok
▸ codex task started · configured model
▸ codex scanning repository…
▸ codex thread + diff ready
The recipe connects Poke to your local bridge
Poke
Add the Pokedex recipe to your Poke, then ask for work in a named workspace.
Pokedex relay
The local HTTP MCP relay validates the shared token and forwards typed tool calls.
Codex Local Server
Runs on your computer, enforces workspace access, and drives the Codex Local Server for each request.
A focused Codex remote, one recipe away
Start & resume tasks
Kick off Codex work in an authorized workspace, continue an existing thread, or resume one later.
Plans & reviews
Ask Codex to plan in read-only mode, then run a review on the same local workspace.
Status & usage
List local tasks, sessions and threads, and read the latest token usage Pokedex has seen.
Threads & diffs
Read stored Codex threads and fetch git diffs from authorized workspaces.
Full Codex controls
Override model, reasoning effort, verbosity, approval policy, web search, and sandbox per supported task call.
Read-only by default
Codex can look but not touch, unless you explicitly allow writes — per agent and per workspace.
Built in the open.
Pokedex is independent, MIT-licensed open source — CLI, agent, relay, and protocol live in one repo. Issues, ideas, and pull requests are welcome.