After opening the AI chat once, BTT keeps sending ⌘C after every double-click, even after the chat is closed (games read it as "c")

Bugs or Unexpected Behavior
1

BTT 6.990 (2026102901), also on 6.954 · macOS 27.2 (26B123) · MacBook Pro (Mac15,9)

Summary

Once the AI chat window has been opened, BTT sends ⌘C to the frontmost app shortly after each double-click, and after some click-drag releases. This continues after the chat window is closed, until BTT is quit.

Apps that expose the selected text through Accessibility don't get the keystroke. Apps that don't, such as games, do. Wuthering Waves ignores the ⌘ and treats it as a plain c press, which opens an in-game menu every time I double-click.

Steps to reproduce

  1. Quit and relaunch BTT. Double-click inside Wuthering Waves (native Mac build, com.kurogame.wutheringwaves.global). Nothing extra happens.
  2. Open BTT's AI chat window. (closed or not, issue persists till BTT restart)
  3. Go back to the game and double-click, or click and drag.

Expected: No synthesized keystrokes. Watching the selection for the AI chat stops when the chat closes.
Actual: About 50–300 ms after each double-click (and some drag releases), BTT sends ⌘ down, c down and up, then ⌘ up. This keeps happening until BTT is quit. Reopening the AI chat brings it back immediately.

Evidence

I logged events with a listen-only CGEventTap at the session level, recording kCGEventSourceUnixProcessID and kCGEventSourceUserData for each one (BTT 6.954; target app is the game):

13.254  leftMouseDown clickState=2              src=hardware
13.353  leftMouseUp   clickState=2              src=hardware
13.558  keyDown  kc=8 "c" flags=0x20100000 (⌘)  src=BetterTouchTool  userData=5645655
13.560  flagsChanged kc=55 flags=0x100000 (⌘)   src=BetterTouchTool
13.561  keyUp    kc=8 "c" flags=0x20100000      src=BetterTouchTool  userData=5645655
13.562  flagsChanged kc=0  flags=0x0            src=BetterTouchTool
13.562  flagsChanged kc=55 flags=0x0            src=BetterTouchTool
  • Counts: in about 1.5 minutes, 9 injected ⌘C, all sent to the game. During the same capture, 3 double-clicks and 2 drags in an app that exposes its selection through Accessibility got none.
  • Not my config: no trigger in my setup sends ⌘C or key code 8. I checked get_triggers and the data store, including disabled and trashed items.
2

I think there was a bug that could cause this in some ai configurations. Can you check whether 6.991 resolves this for you?

3

Sorry, I thought I had checked alpha updates. The bug seems to be gone in the alpha.

4

I just uploaded that alpha after your report! Thanks for testing!