{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreihxzojkwnxp5odwuvhtgchixlznddvqr4sxlouonxshpvwc3rkjkq",
"uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml3tbpkyiqc2"
},
"path": "/t/feature-request-diff-preview-granular-accept-reject-workflow-in-openai-codex-vs-code-extension/1375304#post_11",
"publishedAt": "2026-05-05T08:33:34.000Z",
"site": "https://community.openai.com",
"textContent": "The entire Codex has this mentality of exactly what OpenAI says.\n\n> Right now the Codex extension applies edits directly, which is fast,\n\nGuys, that’s NOT ok. The goal of an AI is to work WITH the human, the human reviews and guides the code in real time. An AI that makes rapid changes with out human interaction is a danger, just look at any time AIs have torpedo database, or just delete changes Hell I’ve already seen it delete whole sections of code and render functionality broken. Code Review tools MUST be important and they MUST be done BEFORE changes are made. It’s been 3 months, but what I’m observing from using it makes me think the goal is “Speed over interactivity”.\n\nThat’s great for vibe coders, but no serious programmer is willing to trust any AI that much , at least not at first.\n\nThree things that need to change if Codex is to be taken seriously.\n\nA. Request based READs, not writes, but even reading files. Opening a directory doesn’t mean “Read anything you want in it” unless the user choose that.\n\nB. Default to permission based systems rather than giving AIs carte blanche to do what they want. Also make those options able to be set up.\n\nC. Allow users to properly code review changes BEFORE they are implemented, not after they are implimented. This is so obvious, I can’t believe anyone thought this tiny diff is acceptable.\n\nMaybe OpenAI doesn’t want a real programmer using this, maybe you only want people who blindly trust the AI and allow it to do anything, but I’ve already seen enough destroyed projects because an AI had that much control. All you’re doing is creating a bad product that will get a bad reputation not because of user action but because of user inaction, and hidden features that are standardized by the industry already.",
"title": "Feature request: Diff preview + granular accept/reject workflow in OpenAI Codex VS Code extension"
}