Activation vs. Keystroke Delivery

The super paste bug reveals a subtle distinction in how operating systems handle inter-process communication. When the code calls tell application "X" to activate, it's using AppleScript's application-level activation model—the same mechanism as clicking an icon in the Dock. This brings all of the target app's windows to the front and makes it the active application, which is far more disruptive than simply delivering a keystroke to the already-focused window.

The fix draws on a principle from Unix's "do one thing well" philosophy: if the target application is already frontmost, there's no need to activate it. System Events can deliver keystrokes to the focused process directly. The activation is only necessary when Field Theory's own UI is in the foreground and we need to return focus to where the user was working. But even then, calling activate is overkill—hiding our window is sufficient. macOS's window server maintains a focus stack, and when the frontmost window disappears, focus naturally returns to whatever was behind it. This mirrors how clipboard managers like Alfred and Raycast handle paste operations—they rely on the OS's existing focus state rather than forcing a full application switch. The difference is like the distinction between asking someone to "come to the front of the room" versus simply handing them a note where they're already standing.