Why am I get asked every time when codex use mcp????
Resolved 💬 5 comments Opened Mar 29, 2026 by Tony7817 Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
You should not add thie feature because the codex cli now become a stupid agent that ask me every time when it use mcp.
What feature would you like to see?
Some mcp have different command arguments each time. Even if I clicked always allow, next time it still ask me if the argument changed. Very stupid design and made my coding process very ineffient. If you don't imporve. I am going to use Claude
The PM should by fired btw.
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I'm not sure if this is a bug report of a feature request. If you want to file a bug report, please create a new issue and fill out the requested information in the bug report template and give it a title that indicates the bug rather than a question.
Please re-open, this is a bug.
Codex asks the user to Allow / Allow for this session / Always allow, and obviously Always allow does not work as expected.
@3rd, if you're experiencing an issue here, please open a new bug report with the information request in the bug report template. This issue is missing most of the information we'd need to investigate.
``
Calling browser.browser_click({"element":.....})``has to be approved even when --sandbox danger-full-access was passed in when starting up. You have allow browser.1 browser.2 actions one by one.
I am not sure how can I allow browser.* with MCP. I think this is what OP might be talking about. This is probably some configuration somewhere.