Can't use KeeAgent with Tabby SSH Client

[Stefomat]

I use KeePass 2.53.1 with KeeAgent 0.13.4. This works wonderfully for PuTTY and WinSCP. Unfortunately, the SSH client Tabby does not recognise KeeAgent. The normal Pageant in version 0.77 is recognised without problems, but KeeAgent is not. Does KeeAgent behave differently from PuTTY Pageant in some respects? How can I debug this problem? Is it a Tabby problem or a KeeAgent problem? Thanks!

[dlech]

You can run KeeAgent from source using Visual Studio to debug the problem.

[dlech]

Did you manually select the agent connection type? Selecting Pageant seems to work but Named Pipe had some issues until I fixed #362.

[Stefomat]

I can reproduce the following behaviour:
Agent type set to Automatic:
No agent is found with KeeAgent started ("SSH ! Agent auth selected, but no running agent is detected").
Without KeeAgent started, password Auth is used.
Agent type set to Pageant:
With KeeAgent started, the agent is found and used.
Without KeeAgent started, it does not fall back to password Auth, Auth fails completely.
Agent type on Named Pipe:
Doesn't work at all, probably because I don't know which path to specify.

I have not yet been able to debug the problem with VSCode, due to lack of time and skills.

[dlech]

Did you try with v0.13.5 (just released yesterday)?

For the named pipe option, you have to enable Windows OpenSSH in the global options. You don't have to specify a path - the default one is correct.

[Stefomat]

Yes i have also tried with v0.13.5, thats the version my last comment is based on.