10 people reported
All time, since Sep 30, including 9 thumbs-up on GitHub.
Dot tasks missing browser tools
“Creating a fresh dot task did not restore them.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/14821/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Dot computer tasks lack browser and desktop tools after MCP startup failures. Tasks reported as hostId=durable can still run Windows PowerShell, but lack browser/desktop tool entry points that local chats have; a fresh task did not help.
Is this your bug?
File my report- Where
- Computer tasks
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Part of: Dot can't access local threads12 bugs
- Dot cannot read local threads57 people
- Dot cloud task create and continue fail with UNKNOWN18 people
- Dot task coordination fails15 people
- list_threads/read_thread fail6 people
- codex_app MCP fails in dot tasks3 people
- Dot can't reach local threads7 people
- Existing thread read fails5 people
- Dot local task creation fails3 people
- Thread tools missing from tasks5 people
- Remote session read fails5 people
Show all 11Show only the largest 10
- Dots tasks missing browser tools5 people
Not quite your bug?
- Delegated tasks lack Computer Use35 people
- MCP tools missing in tasks13 people
Original reports1, newest first
- [Windows][dot/Work] Computer tasks lack browser/desktop tools: durable MCP startup failures and follow-up path errorOn GitHub#49488