Rank, 14 days: 132 on the Claude Code sheet
3 people reported

All time, since Oct 6, including 1 thumbs-up on GitHub.

builtinBrowser desktop keys unsupported

“It drops them from /user/bootstrap, so the built-in browser cannot be turned on for Claude Desktop in gateway mode at all.”

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/claude-code/issues/3931/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

Gateway rejects or drops builtinBrowser keys in desktop policy block. Gateway reports "unknown desktop key" for builtinBrowserEnabled at boot, or later omits builtinBrowser* keys from /user/bootstrap, so the built-in browser stays off.

Is this your bug?

File my report
Where
Claude apps gateway
Error text
builtinBrowserEnabled: unknown desktop key — fix the typo, or upgrade the gateway if this key was added in a newer Claude Desk
Versions
2.1.311 to 2.16120.0
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Claude apps gateway 2.1.311 drops builtinBrowser* desktop keys from /user/bootstrap ("unknown desktop key"), built-in browser unusable in gateway mode (follow-up to #100016)#105369
  2. Claude gateway rejects builtinBrowserEnabled in policy desktop block#100016

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.