Skip to content

Commit f1f039f

Browse files
committed
Added note about the registry key to detect the copilot key provider app
1 parent 224c7f5 commit f1f039f

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

hub/apps/develop/windows-integration/microsoft-copliot-key-provider.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,3 +58,14 @@ The following table *uap3:AppExtension* describes the attributes of the **uap3:A
5858
## Sign your Windows Copilot hardware key provider
5959

6060
Provider apps must be signed in order to be enabled as a target of the Microsoft Copilot hardware key. For information on packaging and signing your app, see [Package a desktop or UWP app in Visual Studio](/windows/msix/package/packaging-uwp-apps).
61+
62+
## Query for the current Copilot hardware key provider
63+
64+
Check if your app is the user's target for the Copilot hardware key & Windows key + C keyboard shortcut by querying the value of the following registry keys. For more information, see [Retrieving Data from the Registry](/windows/win32/sysinfo/retrieving-data-from-the-registry).
65+
66+
| Registry key | Description | Value |
67+
|--------------|-------------|-------|
68+
| HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\BrandedKey\BrandedKeyChoiceType | Identifies if the user has selected either Search or an app as the target of the Copilot key. | "Search" or "App" |
69+
| HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\BrandedKey\AppAumid | Identifies the Application User Model Id (AUMID, also known as AppId) of the Copilot hardware key provider that was last configured, even if the key is currently configured to Search. | An AUMID. |
70+
71+
To provide a good user experience, apps should be respectful of the user's selection for the Copilot hardware key provider app and should not display persistent or noisy requests for the user to change their selection.

0 commit comments

Comments
 (0)