Desktop app: 'Allow Claude to start dev?' dialog not covered by bypass permissions, no always-allow option

Summary

In the Claude Code desktop app, with the permission mode set to Bypass permissions, Claude starting a dev server through the app's browser-preview flow still triggers an approval dialog:

Allow Claude to start dev? Runs in <project>/.claude/worktrees/<worktree-name> on port 3000 npm run dev [Deny] [Allow once]

The dialog only offers Deny / Allow once — there is no "always allow" option, and I couldn't find a settings.json permission rule that suppresses it, so it re-appears on every dev-server start.

Expected behavior (either of these would resolve it)

1. Bypass-permissions mode also covers the dev-server start confirmation, or
2. The dialog gains an "Always allow for this project" option (or a documented settings rule), so it only needs to be approved once per project.

Environment

• Claude Code desktop app on macOS (Darwin 25.5.0)
• Session running in a git worktree
• Dev server defined via .claude/launch.json and started through the in-app browser preview (preview_start)
• Permission mode chip in the composer showed Bypass permissions at the time the dialog appeared

Notes

The permission-modes docs say bypassPermissions skips prompts except a few categories, including "desktop actions where Claude always asks first," but the only named example is archiving a session — the dev-server dialog isn't documented. If it's intentionally in that always-ask category, documenting it (and adding a per-project "always allow") would help; if not, it looks like a gap in bypass-permissions coverage.