Permission-decision prompt overlays keyboard on iPhone, causing accidental taps

Status Open
Maintainer reply None cached
Activity 1 comment · opened Jul 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of the Claude app for iOS available on the App Store

What's Wrong?
On the Code tab of the Claude app for iOS, when a permission/decision prompt appears (approve / always allow / deny for a tool call), it renders overlaid on top of the on-screen keyboard rather than from the top of the screen. If the user is actively typing when the prompt appears, it's very easy to accidentally tap the wrong option — including "always allow," which has effects beyond a single mis-tap.

What Should Happen?
The permission-decision prompt should render from the top of the screen, clear of the keyboard's touch area, so it cannot be triggered by continued typing.

Steps to Reproduce

  1. Open a Claude Code session in the Code tab of the Claude app for iOS.
  2. Start typing a prompt so the on-screen keyboard is up.
  3. Trigger any action that requires a tool-permission decision (e.g. a file write, bash command, or similar) so the approve/always-allow/deny prompt appears.
  4. Observe that the prompt renders overlaid on the keyboard rather than from the top of the screen.
  5. Continue typing (or tap where you intended to type) — it is very easy to instead hit approve, always allow, or deny by accident before noticing the prompt has appeared.

Device / App Version

  • Device: iPhone 17 Pro (Model MG8N4X/A)
  • iOS version: 27.0
  • App: Claude by Anthropic (iOS), Code tab
  • Note: this report doesn't use the CLI-specific fields (claude --version, Terminal/Shell, Platform, OS) in the standard bug report template, as this bug is in the mobile app UI rather than the CLI.

Is this a regression?
I don't know — this is the first time I've used the Code tab's permission-prompt flow on iOS.

Additional Information
None at this time.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗