{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicwpzpkte5ac4wgk7gs26ahzru65ujoe4qnkrvvbm3da45af2dfii",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3meo65vuehdt2"
  },
  "path": "/t/feature-request-plan-mode-add-an-optional-message-box-when-confirming-plan-execute-in-codex-vs-code/1374051#post_1",
  "publishedAt": "2026-02-12T13:38:28.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’ve been really enjoying Codex, and a lot of the community workflows/guides here have genuinely improved how I use it. I’m currently using the VS Code extension on Windows (and patiently waiting for the standalone app).\n\nOne workflow that’s been working great for me is doing a final **Plan mode** pass before I let Codex execute.\n\n**Issue:** I often rely on a small set of “execution directives” (commands/rules) that I provide right before execution (e.g., constraints about which files to touch, how to run tests, logging, safety checks, etc.). In normal execution, Codex respects these really well.\n\nBut in **Plan mode** , after Codex produces the plan, the UI only lets me click **Approve/Implement Plan** (or deny). There’s no place to attach those directives at the moment of execution. Even if I put instructions in `AGENTS.md` like “when in Plan mode, always apply these directives,” it still sometimes proceeds and then later says something like: “Since you didn’t provide your commands, I didn’t do X.”\n\n**Suggested fix / UX tweak:**\nAfter Codex presents the final plan and we click Approve/Implement, add an **optional message box** that gets sent along with the “Implement Plan” action. That way we can add last-second constraints/directives that should apply during execution, without having to redo the entire plan or hope it picks it up from docs.",
  "title": "Feature request (Plan mode): add an optional message box when confirming Plan → Execute in Codex VS Code"
}