Skip to content

feat(settings): Hint users to enable WindowTitles for richer awareness #916

Closed

Description

@omesser

Why

Window titles stay off by default and require consent (Settings → WindowTitles / platform Screen Recording or Screen Cast). That keeps a single cross-OS rule and avoids surprising reads.

Without a nudge, many users never enable the row, so list_windows / describe_screen / ai-buddy://windows stay title-less and the buddy looks less aware than it could be.

Done when

  • When titles would help (e.g. first sensing use, describe_screen, or Harness attach) and usable(WindowTitles) is false, the product surfaces a short, dismissible hint that points at the Settings control to enable window titles.
  • Hint copy is titles-oriented (richer awareness / know which window), never Capture / screenshot foreshadowing.
  • Enabling via the hint path ends at the existing Settings consent flow (wanted ∧ OS grant); no silent grant.
  • Cross-OS: same product rule; platform labels may still say Screen Recording / Screen Cast.

Out of scope

  • Changing the default (titles remain off until the user opts in).
  • Reintroducing Capture or Screenshot portal.
  • Auto-prompting the OS dialog without an explicit Settings / hint action.

Related

— Cursor agent (Architect), on @omesser's behalf.

Activity

  1. added
    enhancementNew feature or request
    p2Eventually: real, but nothing waits on it
    on Sep 22, 2026
  2. added this to the V1 milestone on Sep 22, 2026
  3. self-assigned this
    on Sep 23, 2026
  4. moved this from Todo to In Progress in Fidgeton Sep 23, 2026
  5. omesser commented on Sep 24, 2026

    @omesser
    OwnerAuthor

    Partial progress from #965 (on main)

    Shipped (docs only): Dated design proposal at docs/design/window-titles-hint.html (also indexed and Pages-allowlisted). Reworked against ADR-0032 / #979: one consent gates titles and application names; hint copy is "The buddy knows where your windows are, not what they are"; shape is NamesHint { Quiet | Due | Dismissed } with Due at the request seams. Three surface variants (chat notice / speech bubble / menu-bar badge) are mockable for a decision; none is product code.

    Still open (acceptance):

    • Pick which surface ships.
    • Implement the dismissible hint so that when names would help and usable(WindowNames) is false, the product points at the Settings consent row.
    • Hint path ends at the existing Settings consent flow (no silent grant).

    Per the PR: closes nothing; implementation follows once a surface is chosen. Leaving this issue open.

    — Cursor agent (Coder), on @omesser's behalf.

  6. omesser commented on Sep 27, 2026

    @omesser
    OwnerAuthor

    Shipped on main via #1045

    Merge commit 62b3dc6f — Chat notice when a window read returns geometry without names and names consent is not usable (design variant A).

    Acceptance check:

    • Dismissible hint when names would help and usable(WindowNames) is false — Chat notice armed from windows a tool actually returns; empty desktop / no-geometry platforms stay quiet.
    • Titles/names-oriented copy: "The buddy knows where your windows are, not what they are." (no Capture / screenshot foreshadowing).
    • Open Settings focuses the Privacy row and leaves the box unchecked; no silent grant. "Don't show this again" writes names_hint_dismissed only.
    • Same product rule cross-OS; platform consent labels unchanged.

    Speech bubble and menu-bar badge were design alternatives, not acceptance — intentionally out of this PR.

    Leaving closed as completed.

    — Cursor agent (Coder), on @omesser's behalf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestp2Eventually: real, but nothing waits on it

Projects

  • Status
    Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions