WSL doesn't expose existing Windows named pipes by default, which Cord needs. To work around that, usesocat andnpiperelay.This method is based onthis gist.

1. Installsocat in WSL:sudo apt install socat

2. Getnpiperelay.exe fromhere and place it in a path accessible from WSL, preferably add it to PATH.

3. Add thisnvim alias in your.bashrc,.zshrc, etc.:

   nvim() {if! pidof socat> /dev/null2>&1;then         [-e /tmp/discord-ipc-0 ]&& rm -f /tmp/discord-ipc-0         socat UNIX-LISTEN:/tmp/discord-ipc-0,fork \             EXEC:"npiperelay.exe //./pipe/discord-ipc-0"2>/dev/null&ficommand nvim"$@"}

   Do note that you must either add the path to npiperelay to your Windows PATH, or specify an absolute path to it insideEXEC.Always launch Neovim using this alias in WSL.

You can forward the Discord IPC socket over SSH.This article explains how.

Usearrpc as a bridge. Follow its instructions closely at your own risk.

Cord can work with custom clients, although we do not endorse them, and cannot guarantee that they will work. The main issue is that custom clients often cannot/do not expose the IPC pipe at the same path as the official client, so you might need to create a symlink to make it work.

You can also override the defaults by setting theadvanced.discord.pipe_paths field to a list of absolute paths to use when connecting to Discord.