Why might FAR WinSCP manager not work with SSH CHROOT?

Question

SSH

Given:
There is a Debian Stretch with isolated CHROOT SSH user.
From the console and, for example, from PHPStorm, everything works as it should.
But when I use Far WinSCP Manager - I can't edit, read or create files - when I try to do it - just nothing happens.
At the same time, if I type "ls>test" in the Far command line, the file is perfectly created.
Can this happen if the manager doesn't find bash?
But why does the command line work then?
I'd love to hear any ideas.

Answer 1

Terminal type or encoding, apparently?
Compare those where they work, compare those where they don't work.