Poke, meet your local Codex.
Pokedex is a secure MCP bridge that lets Poke control the Codex agent on your machine — without giving it shell access or your filesystem. Codex stays home, under your policy.
Text Poke. Codex does the work.
Send a message from any Poke interface — the task lands safely inside an authorized workspace on your machine.
project and tell me what it does.
poke ▸ on it — handing this to your local Codex…
you ▸ Now review the code and flag bugs
or risks.
poke ▸ starting codex_review in read-only mode…
▸ agent workspace pokedex · alias resolved
▸ agent sandbox read_only · policy ok
▸ codex task started · model gpt-5-codex
▸ codex scanning repository…
▸ codex transcript + diff ready
Three ingredients between you and Codex
Poke
The interface. iMessage, WhatsApp, web — wherever Poke lives, that's your Codex remote.
Relay MCP
The public HTTPS endpoint. Validates auth, forwards typed requests. Never touches your files.
Local Agent
Runs on your computer, connects outbound, enforces policy — then drives Codex in authorized workspaces.
A full Codex remote, one message away
Start & resume tasks
Kick off Codex tasks in any authorized workspace, continue them later, or resume a previous session.
Plans & reviews
Ask for implementation plans before touching code, or run a full code review that flags bugs and risks.
Status & usage
Read job state and token usage at any time — know what Codex is doing and what it costs.
Transcripts & diffs
Redacted transcripts of every session, plus git diffs of exactly what changed.
Full Codex controls
Switch model, reasoning effort, verbosity, speed mode and sandbox — from a chat message.
Read-only by default
Codex can look but not touch, unless you explicitly allow writes — per agent and per workspace.
Poke never sees your filesystem
Poke can only call typed MCP tools. Real paths stay on your machine — workspaces are exposed through safe aliases.
Build your bowl.
Open source, developer-first, and ready in minutes. Bring Poke and Codex together — safely.