5 people reported
All time, since Sep 30, including 4 thumbs-up on GitHub.
Dots tasks missing browser tools
“A dot connected to an authorised, online Windows PC can expose the supported browser and local Codex session tools in its local tasks.”
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/14769/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
Connected-computer dot tasks lack browser and session tools. Edge is installed and enabled but absent from the task's mention menu; the same computer's desktop-local task initialises those tools.
Is this your bug?
File my report- Where
- Dots local tasks
- Versions
- 0.159.2
- 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
- Dot tasks missing browser tools10 people
Not quite your bug?
- MCP tools missing in tasks13 people
Original reports1, newest first
- Windows MSIX: Dots connected-computer tasks lack browser and session tools; generated app-tools working directory points outside virtualised app dataOn GitHub#49562