[BUG] Mobile Regression: Approve control no longer available from the Code tab session list — each pending permission now requires opening its session (Android + iPadOS)

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

### What's Wrong?

Until the September 11, 2026 app update, the session list in the Code tab of the Claude mobile app exposed an Approve control for sessions blocked on a permission prompt. With several Remote Control sessions running in parallel, I could see which ones were waiting and clear them all from that one screen.

After that update the control is gone. The list still indicates which sessions need attention, but approving requires tapping into a session, approving, and tapping back out — per session, per prompt. This is a huge regression in my workflow.

The change is present on both my Android phone (Play Store update dated September 11) and my iPad, so it does not appear to be specific to one client build.

### What Should Happen?

Pending permission prompts can be approved or denied directly from the session list, without opening each session.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

1. Start several Remote Control sessions across different projects (in my case via `/remote-control` in the VS Code extension).
2. Let several of them hit tool-permission prompts at roughly the same time.
3. Open the Claude app and tap **Code** to reach the session list.
4. Observe that no Approve/Deny control is available at the list level.

### Claude Model

Sonnet (default)

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

1.260910.12

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

VS Code integrated terminal

### Additional Information

I'm a solo developer and I commonly run between 5 and 9 Remote Control sessions in parallel. Managing permission prompts from my phone is the primary reason I use Remote Control at all.

The list-level Approve made triage a single-screen operation: open the app, see what's blocked, clear it. Without it, every approval costs three interactions instead of one, and with 5–9 sessions that multiplies into real friction — parallel work effectively serializes, because sessions sit blocked while I tap through the others one at a time.

This is a regression for multi-session use specifically. For a single session the new layout costs nothing, which I suspect is the workflow it was designed around.