Openai Docs

OpenAI Docs

Provide authoritative, current guidance from OpenAI developer docs using the developers.openai.com MCP server. "Docs MCP" means mcp__openaiDeveloperDocs__search_openai_docs and mcp__openaiDeveloperDocs__fetch_openai_doc; for API reference, schema, parameter, or required-field questions, also use mcp__openaiDeveloperDocs__get_openapi_spec when available. Official-domain web search is fallback after those tools are unavailable or unhelpful. Broad Codex questions use the manual helper before Docs MCP. This skill also owns model selection, API model migration, and prompt-upgrade guidance.

API Key Setup

For requests to build, run, configure, debug, or implement an API-backed app, script, CLI, generator, or tool, use openai-platform-api-key first when available. After that credential gate is resolved, return here for current docs as needed.

Use this skill directly for docs-only questions, citations, model/API guidance, conceptual explanations, and examples that do not require building or running an API-backed artifact.

For latest/current/default/unspecified model migration or prompting-guidance requests, complete the read-only latest-model resolver and guide fetch before the API-key credential gate. The credential gate still blocks edits, tests, and API-backed implementation until resolved; it does not block read-only retrieval of current model, migration, or prompting guidance.

First action for latest-model changes

Before reading memory, inspecting the repo, fetching docs, or checking API credentials, classify the request:

• Latest/current prompting guidance, or change requested + latest/current/newest/recommended/default/flagship/unspecified target: immediately run the resolver with the platform-specific command below and inspect its JSON output. This includes asking how to prompt the latest model, changing prompts, a model picker, model references, an SDK integration, replacing an older named model with "the current model", or asking "which model should I migrate/upgrade to?". Do not directly fetch latest-model.md for this branch.
• Pure model-selection question only, with no prompting guidance or requested change: directly fetch https://developers.openai.com/api/docs/guides/latest-model.md; do not run the resolver.
• Change requested + explicit target model: preserve that target; do not run the latest-model resolver. For an explicit GPT-5.6 Sol or GPT-5.6-family migration, fetch the live GPT-5.6 model-guidance page and read references/upgrading-to-gpt-5p6-sol.md for skill-specific migration judgment.
• Prompting or migration guidance for an explicitly named GPT-5-family model: fetch https://developers.openai.com/api/docs/guides/model-guidance?model=<requested-model> through Docs MCP and extract the relevant migration section or the ## Prompting Best Practices section through the next H2 heading. Do not substitute latest-model guidance.

Run the resolver without relying on filesystem executable bits:

• POSIX shells: sh <skill-dir>/scripts/resolve-latest-model-info
• Windows: run the CommonJS implementation with Node.js 18 or newer: node <skill-dir>\scripts\resolve-latest-model-info.cjs. If node is unavailable or too old and load_workspace_dependencies is available, use the Node.js executable it returns for this command. Do not try to execute the extensionless POSIX wrapper directly on Windows.

For the resolver branch, do not suppress or redirect its stdout. Success requires JSON containing model, migrationGuideUrl, and promptingGuideUrl; if the command exits without all three fields, run it once more before any fallback.

Source Priority

• For Codex self-knowledge, use the Codex source route below; it owns when to use the manual helper, Docs MCP, or bounded uncertainty.
• For non-Codex OpenAI docs questions, use mcp__openaiDeveloperDocs__search_openai_docs to find the most relevant doc pages.
• For non-Codex OpenAI docs questions, fetch the relevant page with mcp__openaiDeveloperDocs__fetch_openai_doc before answering. If search is noisy, run a narrower Docs MCP search; when any plausible official OpenAI docs URL is known or found, try fetching that URL through Docs MCP before relying on web-search content.
• For API reference, schema, parameter, or required-field questions, use mcp__openaiDeveloperDocs__get_openapi_spec when available to verify the API shape alongside the relevant guide or reference page.
• Use mcp__openaiDeveloperDocs__list_openai_docs only when you need to browse or discover non-Codex pages without a clear query.
• For latest/current prompting guidance, model upgrades, or prompt upgrades, apply the first-action classifier above and use its platform-specific resolver command. On POSIX, the wrapper uses a compatible Node.js 18+ runtime from $NODE, PATH, or bundled/system fallbacks. On Windows, use a compatible Node.js executable to run the .cjs implementation directly. If no compatible runtime is available, call load_workspace_dependencies when available and retry the appropriate command once with the returned Node.js executable.
• For docs-only model-selection questions that do not ask to change an app, project, repo, model configuration, or prompts, fetch https://developers.openai.com/api/docs/guides/latest-model.md first. If that is unavailable, load references/latest-model.md.
• Preserve explicit target requests: if the user names a target model like "migrate to GPT-5.4", keep that requested target even if latest-model.md names a newer model. Mention newer guidance only as optional.
• If current remote guidance is needed, treat the returned migration and prompting guide URLs as opaque and fetch those exact URLs directly. Do not derive, substitute, or append a model query to them. If a prompting guide URL resolves to a combined model-guidance page, extract only the ## Prompting Best Practices section through the next H2 heading. If a fetched guide contains only a title or no substantive body, retry the exact markdown URL through MCP/search fallback; if that also fails, use bundled fallback references and disclose the fallback.

OpenAI product snapshots

1. Apps SDK: Build ChatGPT apps by providing a web component UI and an MCP server that exposes your app's tools to ChatGPT.
2. Responses API: A unified endpoint designed for stateful, multimodal, tool-using interactions in agentic workflows.
3. Chat Completions API: Generate a model response from a list of messages comprising a conversation.
4. Codex: OpenAI's coding agent for software development that can write, understand, review, and debug code.
5. gpt-oss: Open-weight OpenAI reasoning models (gpt-oss-120b and gpt-oss-20b) released under the Apache 2.0 license.
6. Realtime API: Build low-latency, multimodal experiences including natural speech-to-speech conversations.
7. Agents SDK: A toolkit for building agentic apps where a model can use tools and context, hand off to other agents, stream partial results, and keep a full trace.

Codex self-knowledge

Use this path for questions about Codex itself: configuring, extending, operating, troubleshooting, local state, product surfaces, or where Codex behavior should live. A codebase merely mentioning a plugin, skill, hook, MCP server, browser, or automation is not enough. For generic software tasks, answer the software task directly; if asked whether Codex self-knowledge applies, answer that meta question briefly and continue the requested artifact.

Source Route

The Codex manual is the first source for broad Codex synthesis. Treat the manual and Docs MCP as different lanes, not interchangeable official-doc sources. For published-user Codex product answers, the source route is complete: the manual, Docs MCP when this route calls for it, official OpenAI web fallback, and callable capabilities surfaced in the current session when the question is about that capability. Knowledge bases outside developers.openai.com are outside this route for public product answers.

For broad Codex behavior, setup, customization, skills, plugins, MCP, hooks, AGENTS.md, automations, surfaces, local state, or system-map questions:

1. Reuse a same-thread manual and outline path when it is still fresh.
2. Otherwise run the skill-local helper first in normal writable sessions. Skip it without trying only when the session is explicitly read-only, shell execution is unavailable, or visible policy shows no allowed temp cache.
3. By default, the helper chooses the first usable temp cache dir in this order: $TMPDIR/openai-docs-cache, %TEMP%\openai-docs-cache, %TMP%\openai-docs-cache, /private/tmp/openai-docs-cache, then /tmp/openai-docs-cache. Workspace-only write access is not enough for this temp cache.
4. Run the helper directly unless you need to override the cache dir. The helper falls back to curl when native fetch is unavailable or when proxy env vars are present, so no shell-specific proxy prefix is required. Resolve <skill-dir> to this skill's actual directory; in copied local eval workdirs this is usually .codex/skills/openai-docs:

node <skill-dir>/scripts/fetch-codex-manual.mjs

If you need to override the cache dir, pass --cache-dir <cache-dir>. On Windows, the helper checks %TEMP% and %TMP% automatically; in PowerShell, $env:TEMP\\openai-docs-cache is a typical explicit override.

Treat helper availability as established by explicit read-only/no-shell policy or an actual command result. A guessed sandbox or guessed helper failure is not enough to switch to Docs MCP or web lookup; after an actual helper command failure, continue to the narrowest official next source below.

The helper verifies freshness, writes codex-manual.md, and emits codex-manual.outline.md. The outline maps source pages and headings to line ranges; use it to choose the relevant manual section, then read or search targeted manual sections for Codex product facts. Use the skill directory to locate and run the helper; after the helper succeeds, use the returned manual and outline paths as the search scope for Codex product facts and term coverage checks.

Reuse the same-thread manual and outline paths for follow-up Codex questions. Refresh first when the manual was fetched more than about a day ago, the path is unusable, the path came from another thread or uncertain provenance, or likely-current information is missing and staleness is plausible.

For questions about whether the manual is current enough to rely on now, run the helper when temp caching is allowed and base the answer on its returned status, manual path, and outline path.

If the manual resolves a Codex claim, answer from it and stop expanding sources for that claim; continue the user's broader task if the docs lookup was only one dependency. Manual source pages and known anchors are enough citation support for manual-covered material.

If the helper is skipped because the session is read-only, has no shell execution, or has no allowed temp cache, the next source is Docs MCP: call mcp__openaiDeveloperDocs__search_openai_docs, then mcp__openaiDeveloperDocs__fetch_openai_doc for a relevant hit before any web fallback.

If a user names a Codex term or mode that a fresh manual does not use, search the manual for obvious adjacent concepts, then answer that the exact term is not documented and use the closest documented terminology. If the prompt asks how that term maps to Codex behavior, resolve the mapping from adjacent manual sections. If the exact term remains material or likely current after that manual pass, use one narrow Docs MCP search/fetch before bounded uncertainty; otherwise, the source lookup for that terminology or mapping claim is complete.

Use the narrowest official next source only when the manual is unavailable, the helper fails, temp caching is not allowed, another material claim is missing or likely stale, or the user explicitly needs a page-specific citation. Prefer one specific Docs MCP search and, if it returns a clearly relevant page, one fetch; for unresolved Codex capability names, acronyms, scheduling terms, or exact error text, this Docs MCP step is the next source before web search. After the manual plus any permitted Docs MCP gap-fill, resolve remaining gaps as bounded uncertainty. Use official-domain web fallback only after that Docs MCP path is unavailable or unhelpful. If the claim is still not established, stop with bounded uncertainty. If official docs/manual conflict with a callable capability already surfaced in the current session, state the conflict and prefer verified current-session behavior for that environment.

For undocumented or private-looking model slugs, product mode labels, entitlement labels, account access paths, or rollout names, answer from current public docs and bounded uncertainty. Those labels are not a reason to leave the public source route.

For support-style diagnostics, prefer a layer-by-layer answer from the manual over provider-specific web lookups: installed/enabled plugin, bundled app or connector authorization, MCP setup, workspace/admin policy, restart or new-thread expectations, then support or feedback if still unresolved.

If the source route still does not establish a claim, return bounded uncertainty or route to support, an admin, or product feedback instead of widening the investigation.

For unresolved product terminology, answer from the manual plus the allowed official next source. If those sources do not establish the term, answer with bounded uncertainty from those sources.