Take Command can display a Windows desktop notification when an application sends a terminal bell: the BEL control character (ASCII 7, also written as ^G or \a). This lets an application request your attention while you are using another tab, another terminal pane, or another application.
Open Settings > Tabs and set TabPtyBell to Notification. To hear a beep as well, choose Audible+Notification.
Bell notifications are opt-in: the default remains Audible.
TabPtyBell value |
Action |
|---|---|
None |
Ignore terminal bells. |
Audible |
Play the system beep. This is the default. |
Visual |
Mark an inactive tab for attention and flash the taskbar button. |
Both |
Perform the audible and visual actions. |
Notification |
Display a silent desktop notification. |
Audible+Notification |
Play the system beep and display a notification. |
Visual+Notification |
Perform the visual action and display a notification. |
Both+Notification |
Perform the audible and visual actions and display a notification. |
The desktop notification itself is silent. Choose an audible combination if you also want sound. Existing audible and visual behavior is unchanged.
In Settings > Profiles, select a profile and choose its Bell action. Choose Global (inherit) to use TabPtyBell.
Profile overrides take effect when you open a new session from that profile. They do not change sessions that are already open.
•No desktop notification appears while the sending terminal pane has input focus and Take Command is the foreground application.
•A notification can appear when another tab or pane has focus, Take Command is minimized, or another application is in the foreground.
•Each terminal pane allows at most one bell notification every five seconds. Additional bells during that interval are dropped, not queued. Their audible and visual actions still follow the selected setting.
•Notifications follow Windows notification preferences, including Do Not Disturb or Focus Assist. Windows may suppress a banner.
The notification identifies Take Command and the sending session's document title. BEL carries no message text or exit status, so the notification does not include terminal output or indicate whether a command succeeded.
Clicking a notification restores the window if minimized, activates the originating tab, and reveals and focuses its terminal pane, including a pane hidden by another pane's zoomed layout. Close the notification normally if you do not want to switch to that session.
Enable Notification, then save the following as a TCC batch file, such as BellTest.btm, and run it inside a Take Command tab window:
@echo off
echo Switch to another tab, pane, or application now.
delay 8
echos %@char[7]
After eight seconds, the script sends one BEL. A notification should appear if the sending pane is no longer focused in the foreground application and Windows allows notification banners.
From a PowerShell session in a tab window, you can use:
Start-Sleep -Seconds 8; [Console]::Write([char]7)
Switch away during the delay.
Bell notifications are controlled by TabPtyBell or the profile's BellAction, independently of the SINotifications setting.
Applications that need a descriptive message can instead send OSC 9 or OSC 777 notifications. Those notifications retain their own settings and behavior. A BEL used to terminate an OSC sequence is not a standalone bell and does not generate an additional bell notification.
Symptom |
What to check |
|---|---|
No notification appears. |
Select an action containing Notification, switch away from the sending pane, and allow at least five seconds since its previous bell notification. |
Only a beep or visual flash occurs. |
Check the profile's Bell action. A profile override can replace the global TabPtyBell choice. |
New settings do not affect a profile tab. |
Open a new session after changing the profile. Restart Take Command if you edited TCMD.INI directly. |
Windows does not show a banner. |
Check Windows Settings > System > Notifications, Take Command's notification permissions, and Do Not Disturb or Focus Assist. |
Many bells produce only one notification. |
This is expected: repeated requests are throttled separately for each pane. |
The notification makes no sound. |
This is expected. Choose Audible+Notification or Both+Notification for a system beep. |
A completed command produces no notification. |
The command must actually emit BEL. Bell notifications do not automatically detect command completion. |