Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Codex Monitor does not surface MCP browser tool approval prompts, making browser tools appear hung

Open
#612 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
playwright, tauri, typescript

Research direction

Start by reproducing the issue with Playwright MCP calls such as browser_navigate and compare Codex Monitor with Codex CLI, where the approval prompt appears. Trace the Codex Monitor GUI approval-prompt handling and verify that the prompt is shown and that approving it lets the browser action continue.

Written by the indexing model from the issue text.

Description

Codex Monitor appears to hang when Codex uses Playwright/browser MCP tools that require approval. The same action in Codex CLI shows an approval prompt, but Codex Monitor does not present the approval prompt in the GUI.

Because the approval prompt is not visible, the user has no way to approve the tool call, and the session looks like it is stuck indefinitely.

Environment:

  • OS: Linux Mint
  • App packaging: AppImage
  • Codex Monitor version: 0.7.67
  • Playwright MCP/browser tools involved:
    • browser_navigate
    • browser_tabs
    • possibly other browser MCP tools

What happened:

  1. In Codex Monitor, Codex attempted to use browser tools.
  2. The UI appeared to hang for several minutes.
  3. No approval prompt was shown in Codex Monitor.
  4. In Codex CLI, the approval prompt appears normally.
  5. After approving in CLI or adjusting tool approvals, the same kind of browser action can proceed in CM.
Dominant language
TypeScript
Stars
4.3k
Forks
416
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dimillian/CodexMonitor

All issues in Dimillian/CodexMonitor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.