Skip to content

Make terminal beeps highlight Windows Terminal in the taskbar, to get user attention when backgrounded #1608

Closed

Description

Scenario

A long running task is running in the Terminal. The user is using another app.

Something happens requiring attention from the user.

What happens now

The terminal beeps, but the user doesn't know about it, and doesn't see the issue.

What should happen

The taskbar item becomes highlighted, showing that the terminal needs attention (optionally this can be disabled).

Activity

  1. added
    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.
    on Jun 25, 2019
  2. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Jun 25, 2019
  3. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Jun 25, 2019
  4. changed the title [-]Make terminal beeps highlight the Taskbar, to get user attention when backgrounded[/-] [+]Make terminal beeps highlight Windows Terminal in the taskbar, to get user attention when backgrounded[/+] on Jun 25, 2019
  5. DHowett-MSFT commented on Jun 27, 2019

    @DHowett-MSFT
    Contributor

    Yep, we should have some bell support. This also requires us to push bells through the conpty layer. 😄

  6. added
    Product-ConptyFor console issues specifically related to conpty
    Area-UserInterfaceIssues pertaining to the user interface of the Console or Terminal
    Area-VTVirtual Terminal sequence support
    and removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Jun 27, 2019
  7. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Jun 27, 2019
  8. tstackhouse commented on Jun 28, 2019

    @tstackhouse

    Yep, we should have some bell support. This also requires us to push bells through the conpty layer. 😄

    Does this include audible bells? Because I can't for the life of me get audible bells to work.

  9. zadjii-msft commented on Jul 2, 2019

    @zadjii-msft
    Member
  10. bobvandevijver commented on Oct 16, 2020

    @bobvandevijver

    Now that #7793 has been merged, I think this issue will be the main one for tracking the visual bell?
    Anyways, I would love to see both: the audible and visible notification combined, probably with a setting as suggested here.

  11. j4james commented on Oct 16, 2020

    @j4james
    Collaborator

    FYI there is a system-wide option called Show audio alerts visually, which you can set to flash the window border (or even the whole screen), when the bell is triggered. It's probably not exactly what you want, but it may do as temporary solution.

  12. ghost added
    In-PRThis issue has a related PR
    on Nov 10, 2020
  13. ghost closed this as completedin #8215on Nov 18, 2020
  14. ghost removed
    In-PRThis issue has a related PR
    on Nov 18, 2020
  15. ghost added
    Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.
    on Nov 18, 2020
  16. ghost added a commit that references this issue on Nov 18, 2020
    1fbcf34
  17. duaneking commented on Apr 21, 2026

    @duaneking

    FYI there is a system-wide option called Show audio alerts visually, which you can set to flash the window border (or even the whole screen), when the bell is triggered. It's probably not exactly what you want, but it may do as temporary solution.

    And this blatantly discriminates against the blind, if its the only option. I am requesting that the relevant leadership look at the reprioritization of this issue with that in mind. It's impossible for me to show others that Windows is accessible for the disabled if I have the disabled literally telling me this is one of the core issues because it doesn't respect accessibility the same way Linux does; This is a Linux compete issue for you guys and so I was hoping that you would actually put some effort into this.

  18. zadjii-msft commented on Apr 21, 2026

    @zadjii-msft
    Member

    Duane King (@duaneking) friend, I get that you're upset by this bug. You have every right to be! But the right way to deal with this is not necroing a bunch of semi-related threads on the topic.

    File a new issue. Include your terminal version, your settings, probably even your Windows SKU (I know there were issues with playing media on the "N" SKU in the past).

    We'll try and help debug there ☺️

  19. locked and limited conversation to collaborators on Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-UserInterfaceIssues pertaining to the user interface of the Console or TerminalArea-VTVirtual Terminal sequence supportIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Product-ConptyFor console issues specifically related to conptyProduct-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions