@mqs Yeah socat is a dependency if you want to use kitty with it as the kitty integration primarily works through the kitty socket interface. I guess that dependency can be added to the package, it wasn't originally required back when the package was created.

I just wanted to try out xpipe, but started to run into this issue:

java.io.IOException: Unable to launch terminal Kitty: socat executable socat not found in PATH
at io.xpipe.app.util.TerminalLauncher.open(TerminalLauncher.java:73)
at io.xpipe.ext.base.action.LaunchAction$Action.execute(LaunchAction.java:100)
at io.xpipe.app.comp.store.StoreEntryWrapper.executeDefaultAction(StoreEntryWrapper.java:217)
at io.xpipe.app.comp.store.StoreEntryComp.lambda$createSimple$0(StoreEntryComp.java:94)
at io.xpipe.app.util.ThreadHelper.lambda$runFailableAsync$1(ThreadHelper.java:42)
at io.xpipe.app.util.ThreadHelper.lambda$wrap$0(ThreadHelper.java:19)
at java.lang.VirtualThread.run(VirtualThread.java:309)

Caused by: java.io.IOException: socat executable socat not found in PATH
at io.xpipe.app.util.CommandSupport.isInPathOrThrow(CommandSupport.java:31)
at io.xpipe.app.terminal.KittyTerminalType$Linux.launch(KittyTerminalType.java:114)
at io.xpipe.app.util.TerminalLauncher.open(TerminalLauncher.java:69)
... 6 more

Is there a missing (optional) dependency? As the error says, I do use kitty and do not have socat installed.