Can not rekey if any of the additional devices (not a paperkey) don't or can't run run_keybase

Keybase GUI Version: 1.0.18-20161118170023+c298c96

I have a device DemonicDragonsVPS which is a headless VPS instance and any attempt to run 'run_keybase' on it hangs indefinitely, however, this is preventing rekey of a private folder that was never even created or added to from that device. Secondarily, if you launch from cli why is run_keybase FORCED on you to cd /keybase in order to see the following:
user@host $ cd /keybase
user@host $ ls
private public

I petition to remove the requirement that all devices need to run 'run_keybase to rekey and private folders are allowed to rekey via paperkey like public keys ( or that rekeying works for both in one operation).

Proof that a headless instance with keybase is failing to use 'run_keybase' for rekeying is belwo:

fedora@redacted ://:Mon, 21 November 05:42:23 EST ~
0 run_keybase
^C
fedora@redacted ://:Mon, 21 November 05:50:58 EST ~

Start by reproducing the reported hang with run_keybase on the headless VPS and review the rekey flow involving private folders, additional devices, and paperkeys. Compare the CLI behavior around /keybase with the requested rekey paths. Done means a private folder can be rekeyed without requiring every additional device to run run_keybase, while existing public-key rekeying remains functional.