[BUG] Claude Code on the web (claude.ai/code): MCP connector prompts offer only "Allow once", so read-only tools ask on every call

Surface: Claude Code on the web (claude.ai/code), cloud session, Opus 5.5, permission mode "Accept edits". This is not the CLI, so the CLI version and terminal fields don't apply.

What happens
A long build session that uses a connected MCP connector (Railway) stops for approval on every tool call. The dialog ("Allow Claude to use Get logs (Railway)?") has only Deny and Allow once. There is no "Always allow this tool" or "Allow for this session". Get logs is read-only, yet each new deployment ID triggers the prompt again, so an unattended build stalls until someone clicks.

Expected
The same choices the CLI has: allow this tool for the session or always, or allow all read-only tools from a connector. There should also be a way to set this per connector before a session starts, so a long cloud build can run unattended.

Steps to reproduce

1. Connect an MCP connector (e.g. Railway) on claude.ai.
2. Start a cloud session at claude.ai/code on any repo.
3. Ask for a task that calls the connector's read-only tools repeatedly (e.g. polling deployment logs).
4. Every call shows Deny / Allow once, with no persistent option.

Related, not duplicates: #47180 (Cowork scheduled tasks ignore Always allow), #87548 (approval clicked and ignored in a remote session), #74715 (Chrome Always allow saved as once). Here the persistent option is missing from the dialog entirely.