[ktn] vesktop-ktn

Vesktop with real push-to-talk on sway and other compositors without a GlobalShortcuts portal

sudo pacman -S ktn/vesktop-ktn
Version1.6.7.20261003215751.g1039ae3-1
Updated
Upstream basev1.6.7
Pinnedupstream main @ 0ead609 (Electron 44), until a release includes it
Upstreamhttps://github.com/Vencord/Vesktop
Sourcehttps://github.com/Kautiontape/vesktop
Providesvesktop=1.6.7, vencord-desktop=1.6.7
Conflictsvesktop, vencord-desktop
Dependsalsa-lib, gtk3, nss
Retire whenAn upstream Vesktop release ships the vesktop.sock IPC socket (PR #1238); checked by hand, and expect the sync to conflict when it lands

What it is

Vesktop, the Discord client with Vencord built in, plus Vendicated's draft PR #1238. That PR adds global shortcuts and a local IPC socket, $XDG_RUNTIME_DIR/vesktop.sock.

Why it exists

Wayland doesn't let unfocused apps see your keys. The only standard way around that is the GlobalShortcuts portal, and sway's portal doesn't implement it. Even where the portal exists, Electron only reports key presses, never releases, so it can't do hold-to-talk.

The socket solves it: your compositor binds a key or mouse button and sends Start on press and Stop on release. Those drive Discord's own push-to-talk, with its indicator, its sounds and its release delay, while other apps keep a live mic.

echo run-shortcut:pushToTalkNormalStart | nc -N -U "$XDG_RUNTIME_DIR/vesktop.sock"
echo run-shortcut:pushToTalkNormalStop  | nc -N -U "$XDG_RUNTIME_DIR/vesktop.sock"

In sway, bind them to the same key with bindsym --no-repeat and bindsym --release. Set Vesktop's Input Mode to Push to Talk.

How it differs from upstream