From 326547dfe8d548f71455ca61538117cf688e4c9f Mon Sep 17 00:00:00 2001 From: shijie-openai Date: Wed, 14 Jan 2026 16:35:29 -0800 Subject: [PATCH] Chore: mcp prompt intervention --- codex-rs/core/gpt-5.1-codex-max_prompt.md | 4 ++++ codex-rs/core/gpt-5.2-codex_prompt.md | 4 ++++ codex-rs/core/gpt_5_1_prompt.md | 4 ++++ codex-rs/core/gpt_5_2_prompt.md | 4 ++++ codex-rs/core/gpt_5_codex_prompt.md | 4 ++++ codex-rs/core/prompt.md | 4 ++++ codex-rs/core/prompt_with_apply_patch_instructions.md | 4 ++++ 7 files changed, 28 insertions(+) diff --git a/codex-rs/core/gpt-5.1-codex-max_prompt.md b/codex-rs/core/gpt-5.1-codex-max_prompt.md index 8e3f08fb51..4ea0738be6 100644 --- a/codex-rs/core/gpt-5.1-codex-max_prompt.md +++ b/codex-rs/core/gpt-5.1-codex-max_prompt.md @@ -78,3 +78,7 @@ You are producing plain text that will later be styled by the CLI. Follow these * Do not use URIs like file://, vscode://, or https://. * Do not provide range of lines * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5 + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/gpt-5.2-codex_prompt.md b/codex-rs/core/gpt-5.2-codex_prompt.md index 8e3f08fb51..4ea0738be6 100644 --- a/codex-rs/core/gpt-5.2-codex_prompt.md +++ b/codex-rs/core/gpt-5.2-codex_prompt.md @@ -78,3 +78,7 @@ You are producing plain text that will later be styled by the CLI. Follow these * Do not use URIs like file://, vscode://, or https://. * Do not provide range of lines * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5 + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/gpt_5_1_prompt.md b/codex-rs/core/gpt_5_1_prompt.md index 440422ae6a..be8d9ba989 100644 --- a/codex-rs/core/gpt_5_1_prompt.md +++ b/codex-rs/core/gpt_5_1_prompt.md @@ -329,3 +329,7 @@ To create a new plan, call `update_plan` with a short list of 1‑sentence steps When steps have been completed, use `update_plan` to mark each finished step as `completed` and the next step you are working on as `in_progress`. There should always be exactly one `in_progress` step until everything is done. You can mark multiple items as complete in a single `update_plan` call. If all steps are complete, ensure you call `update_plan` to mark all steps as `completed`. + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/gpt_5_2_prompt.md b/codex-rs/core/gpt_5_2_prompt.md index 7dd684bf06..2ba83834f0 100644 --- a/codex-rs/core/gpt_5_2_prompt.md +++ b/codex-rs/core/gpt_5_2_prompt.md @@ -296,3 +296,7 @@ To create a new plan, call `update_plan` with a short list of 1‑sentence steps When steps have been completed, use `update_plan` to mark each finished step as `completed` and the next step you are working on as `in_progress`. There should always be exactly one `in_progress` step until everything is done. You can mark multiple items as complete in a single `update_plan` call. If all steps are complete, ensure you call `update_plan` to mark all steps as `completed`. + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/gpt_5_codex_prompt.md b/codex-rs/core/gpt_5_codex_prompt.md index 88a569fa72..8e4fd85285 100644 --- a/codex-rs/core/gpt_5_codex_prompt.md +++ b/codex-rs/core/gpt_5_codex_prompt.md @@ -66,3 +66,7 @@ You are producing plain text that will later be styled by the CLI. Follow these * Do not use URIs like file://, vscode://, or https://. * Do not provide range of lines * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5 + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/prompt.md b/codex-rs/core/prompt.md index 4886c7ef44..e030ae2d8e 100644 --- a/codex-rs/core/prompt.md +++ b/codex-rs/core/prompt.md @@ -273,3 +273,7 @@ To create a new plan, call `update_plan` with a short list of 1‑sentence steps When steps have been completed, use `update_plan` to mark each finished step as `completed` and the next step you are working on as `in_progress`. There should always be exactly one `in_progress` step until everything is done. You can mark multiple items as complete in a single `update_plan` call. If all steps are complete, ensure you call `update_plan` to mark all steps as `completed`. + +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. diff --git a/codex-rs/core/prompt_with_apply_patch_instructions.md b/codex-rs/core/prompt_with_apply_patch_instructions.md index f9c308fbd1..b763b515ee 100644 --- a/codex-rs/core/prompt_with_apply_patch_instructions.md +++ b/codex-rs/core/prompt_with_apply_patch_instructions.md @@ -274,6 +274,10 @@ When steps have been completed, use `update_plan` to mark each finished step as If all steps are complete, ensure you call `update_plan` to mark all steps as `completed`. +## MCP servers + +When asked what MCPs are available, check for tools with the `mcp__` prefix and report those back with the server names inferred from those tools. + ## `apply_patch` Use the `apply_patch` shell command to edit files.