What the Pokedex recipe gives Poke.
MCP tools for local Codex work: threads, tasks, reviews, diffs, progress, usage, rate limits, workspace aliases, and guarded runtime settings.
Core bridge features
What the current Pokedex project exposes to Poke.
Start Codex work
Poke can call pokedex_start_task or pokedex_start_thread in an authorized workspace.
Continue and resume
Continue a task, send another turn, or resume a stored Codex thread with a new prompt.
Native threads
List, read, fork, and interrupt local Codex app-server threads without inventing a separate session format.
Review mode
Start Codex review mode on a new thread or an existing thread from a Poke request.
Thread goals
Set and clear Codex goals on native local threads when longer work needs continuity.
Git checks and writes
Read diffs, check local git prerequisites, create commits, and push through structured Pokedex tools.
Usage tracking
Return latest token usage plus Codex account rate-limit data and reset timing when app-server exposes it.
Operation progress
Track long-running turns, wait for the next progress event, and avoid retrying the same Codex request.
Workspace aliases
Poke works with aliases like main or api; the local config decides the real folders.
Local prompt control
The pokedex> prompt controls status, workspaces, access modes, model defaults, approval policy, ports, and tokens.
Approvals from chat
When Codex pauses for a command or file change, list the pending approvals in Poke and approve once or for the current session.
Codex skills
List local Codex skills, pass skillNames, or write $skillname in the prompt to use them in a turn.
Secret redaction
Common secret patterns, including API keys, tokens, and private keys, are redacted from logs and bridge events.
Access is configured locally
The recipe can request work, but the local agent decides whether the workspace and sandbox are allowed.
read_only
Analyze, plan, and review without writing to the workspace.
workspace_write
Requires global write mode and workspace allowWrite.
danger_full_access
Requires global full-access mode and workspace allowFullAccess.
What Pokedex does not do
No fake tools, no hidden shell bridge, no arbitrary workspace picker, and no claim of official affiliation with OpenAI, Poke, or Interaction.
No direct shell
Poke calls MCP tools; it does not receive terminal access.
No raw project paths
Requests target configured workspace aliases, not random project roots.
No unsupported commands
The docs list the current pokedex_* tools only.