Codebase Memory MCP approval prompt can become unclickable in Codex voice tasks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
Summary
In a Codex voice task, a Codebase Memory MCP approval prompt appeared with “Allow once” and “Always allow”. Neither option was clickable, leaving the task in a waiting-for-approval state.
Expected behavior
The user should be able to choose an approval option, or the task should provide a recoverable fallback.
Actual behavior
The dialog remained visible but could not be interacted with. The delegated task stayed blocked until it was manually instructed to avoid the MCP and use local code search instead.
Context
- macOS Codex desktop app
- Occurred during a delegated remote project task initiated from voice
- Permission request: Codebase Memory MCP
- No credentials or data were entered
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the macOS Codex desktop app with a delegated voice task that requests Codebase Memory MCP approval. Check whether the “Allow once” and “Always allow” options are interactive and whether the task has a recoverable fallback when approval cannot be completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100