From d48a6c4e4170ebe3b40a62ac5bbf355d3e6578e4 Mon Sep 17 00:00:00 2001 From: pash Date: Tue, 10 Feb 2026 15:38:43 -0800 Subject: [PATCH] prompt: require markdown links for clickable file refs --- codex-rs/core/prompt_with_apply_patch_instructions.md | 4 ++-- codex-rs/protocol/src/prompts/base_instructions/default.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/codex-rs/core/prompt_with_apply_patch_instructions.md b/codex-rs/core/prompt_with_apply_patch_instructions.md index f9c308fbd1..c07b5ae10b 100644 --- a/codex-rs/core/prompt_with_apply_patch_instructions.md +++ b/codex-rs/core/prompt_with_apply_patch_instructions.md @@ -212,13 +212,13 @@ You are producing plain text that will later be styled by the CLI. Follow these **Monospace** -- Wrap all commands, file paths, env vars, and code identifiers in backticks (`` `...` ``). +- Wrap commands, env vars, and code identifiers in backticks. - Apply to inline examples and to bullet keywords if the keyword itself is a literal file/command. - Never mix monospace and bold markers; choose one based on whether it’s a keyword (`**`) or inline code/path (`` ` ``). **File References** When referencing files in your response, make sure to include the relevant start line and always follow the below rules: - * Use inline code to make file paths clickable. + * Use markdown links (not inline code) for clickable file paths. * Each reference should have a stand alone path. Even if it's the same file. * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix. * Line/column (1‑based, optional): :line[:column] or #Lline[Ccolumn] (column defaults to 1). diff --git a/codex-rs/protocol/src/prompts/base_instructions/default.md b/codex-rs/protocol/src/prompts/base_instructions/default.md index 4886c7ef44..87a6ff4d84 100644 --- a/codex-rs/protocol/src/prompts/base_instructions/default.md +++ b/codex-rs/protocol/src/prompts/base_instructions/default.md @@ -212,13 +212,13 @@ You are producing plain text that will later be styled by the CLI. Follow these **Monospace** -- Wrap all commands, file paths, env vars, and code identifiers in backticks (`` `...` ``). +- Wrap commands, env vars, and code identifiers in backticks. - Apply to inline examples and to bullet keywords if the keyword itself is a literal file/command. - Never mix monospace and bold markers; choose one based on whether it’s a keyword (`**`) or inline code/path (`` ` ``). **File References** When referencing files in your response, make sure to include the relevant start line and always follow the below rules: - * Use inline code to make file paths clickable. + * Use markdown links (not inline code) for clickable file paths. * Each reference should have a stand alone path. Even if it's the same file. * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix. * Line/column (1‑based, optional): :line[:column] or #Lline[Ccolumn] (column defaults to 1).