[FEATURE] Android app Code mode: restore input focus after permission dialogs (Bluetooth keyboard support)

Resolved 💬 2 comments Opened Apr 2, 2026 by Atsushi4 Closed May 11, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When using the Claude Android app in Code mode (left sidebar) with a Bluetooth keyboard, the input field loses focus after a permission/approval dialog is dismissed.

During a Code mode session, Claude periodically shows a dialog asking the user to approve an action (e.g. "Allow this tool use?"). After the user responds to the dialog, the input field loses keyboard focus. The user must tap the input field on the screen before they can continue typing.

This forces a screen touch every time a permission dialog appears, making it impossible to operate entirely via Bluetooth keyboard.

Proposed Solution

After a permission/approval dialog is dismissed (whether approved or denied), automatically return keyboard focus to the input field.

This is standard behavior in desktop apps and web applications — when a modal or dialog closes, focus returns to the previously focused element.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

Environment: Android app, Code mode (left sidebar), Bluetooth external keyboard (tablet use case)

Related issue: #42567 (no keyboard shortcut to submit in Code mode) — both issues together make it impossible to operate Code mode with a Bluetooth keyboard without touching the screen.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗