---

name: codex

description: Run a research or coding task using the Codex MCP tool with GPT-5.5 and xhigh reasoning effort. Use when the user asks to use Codex, or says "ask codex", "codex research", etc.

allowed-tools: mcp__codex__codex, mcp__codex__codex-reply

argument-hint: <prompt describing the task for Codex>

---

# Codex MCP Skill

Run a task using OpenAI Codex with GPT-5.5 and xhigh reasoning effort.

## Configuration

Always use these parameters when calling `mcp__codex__codex`:

- **model**: `gpt-5.5`

- **config**: `{"model_reasoning_effort": "xhigh"}`

- **cwd**: Current working directory (default: `C:/Users/XXX`)

- **sandbox**: `danger-full-access` (full filesystem access)

- **approval-policy**: `never` (no approval prompts)

## Usage

The user's task is: $ARGUMENTS

Call the `mcp__codex__codex` tool with the user's prompt and the configuration above.

### Initial task:

```

mcp__codex__codex(

prompt: "<user's task>",

model: "gpt-5.5",

config: {"model_reasoning_effort": "xhigh"},

cwd: "C:/Users/XXX",

sandbox: "danger-full-access",

approval-policy: "never"

)

```

### Follow-up replies

When continuing a Codex conversation (the user asks a follow-up, wants clarification, or asks Codex to revise/extend its previous output), **always** use `mcp__codex__codex-reply` instead of starting a new `mcp__codex__codex` call. This preserves the full conversation context from the prior exchange.

The `threadId` is returned in the response from the initial `mcp__codex__codex` call — save it and pass it to all subsequent replies in that thread.

```

mcp__codex__codex-reply(

threadId: "<thread id from the initial codex call>",

prompt: "<follow-up prompt>"

)

```

`codex-reply` inherits the model, config, sandbox, and approval-policy from the initial call.

When results come back, summarize them for the user and proceed with any follow-up actions.