Skip to content

[Bug]: Control UI input bar occupies nearly full screen in Android PWA landscape mode #98615

Description

@jin-li

Bug type

Behavior bug (incorrect output/state without crash)

Summary

When using OpenClaw Control UI as a PWA ("Add to Home Screen" in Chrome) on an Android phone in landscape orientation, the input bar occupies nearly the entire screen, leaving almost no room to view chat history. There is no way to hide or collapse the input area.

Steps to reproduce

  1. Open OpenClaw Control UI in Chrome on an Android phone
  2. Tap "Add to Home Screen" to install as PWA
  3. Open the PWA from the home screen
  4. Rotate the phone to landscape orientation
  5. Observe that the input bar takes up most of the screen, with minimal space for chat messages

Expected behavior

In landscape mode, the input bar should either:

  • Be compact (similar to portrait mode proportions), or
  • Have a toggle button to hide/collapse the input area so users can browse chat history

Actual behavior

The input bar (text field + attachment/voice/send buttons + model selector) occupies nearly the full vertical space in landscape mode, making it impossible to view meaningful chat history. See attached screenshot.

Image

OpenClaw version

2026.6.11 (gateway)

Operating system

Android (Google Chrome PWA, "Add to Home Screen")

Install method

PWA (Add to Home Screen from Chrome)

Model

N/A (UI layout issue, not model-dependent)

Provider / routing chain

N/A (UI layout issue)

Impact and severity

  • Affected: All Android PWA users in landscape mode
  • Severity: Medium (blocks normal usage — cannot view chat history while composing)
  • Frequency: Always (every time in landscape orientation)
  • Consequence: Users must rotate to portrait to read chat history, then rotate back to landscape to type — poor UX on devices with physical keyboards or stands

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.no-staleExclude from stale automation

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions