Improve handling of small control-strip UIs like OBS #23

Closed
opened 2026-05-01 17:11:57 +02:00 by luna · 1 comment
Collaborator

Problem

Apps like OBS expose critical state through small, app-specific controls (Start Recording, Stop Recording, Start Streaming, etc.). Generic OCR on the whole screen is often too noisy for this.

Desired capability

Add app/control-strip-oriented helpers, or at least better primitives, for small clustered status/action controls.

Examples

  • identify whether OBS is currently recording
  • detect and target Stop Recording
  • distinguish recording vs streaming state from the visible control strip

Why

This class of UI shows up a lot in desktop automation and is currently more painful than it should be.

## Problem Apps like OBS expose critical state through small, app-specific controls (`Start Recording`, `Stop Recording`, `Start Streaming`, etc.). Generic OCR on the whole screen is often too noisy for this. ## Desired capability Add app/control-strip-oriented helpers, or at least better primitives, for small clustered status/action controls. ## Examples - identify whether OBS is currently recording - detect and target `Stop Recording` - distinguish recording vs streaming state from the visible control strip ## Why This class of UI shows up a lot in desktop automation and is currently more painful than it should be.
Owner

bad issue

bad issue
space closed this issue 2026-05-01 17:13:20 +02:00
This repo is archived. You cannot comment on issues.
No Label
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: space/clickthrough#23