I did not want the private key saved on your servers. Also, thought it was terrible that I was unable to copy the public key (from the mac app) and now do not know where it saved the private key :/
If you used the browser to generate your PGP keys (there is a browser PGP wizard) then it will only store an encrypted copy on the server IF you check the box that enables that feature.
If you used the installed keybase app on your computer, then any PGP keys you generate are placed on your GPG keyring and are not sent to the server. You would need to login on the browser and select an option to allow uploading the PGP keys.
As for device encryption keys, those never leave the device.
Config dir can be shown as the parent of keybase config info. The file secretkeys.<you>.mpack is where your secret keys for Keybase account you are stored. You'll have multiple of those files if you have multiple Keybase accounts provisioned for that machine.
Should I use gpg --import /path/to/secretkeys.<you>.mpack to import the keybase secret key into my GnuPGP keychain? I don't know why I'm getting this error"
gpg: no valid OpenPGP data found.
No. The device keys are not GPG compatible.
Oh... Sorry, I'm mistaken, so how should I add this private key to the keychain so that I could decrypt files then? (according to this issue, I should keybase pgp select, yet I have an empty private-key-list)
it is possible to extract private key using keybase cli.
keybase pgp export -s > priv_keybase.txt
Most helpful comment
it is possible to extract private key using keybase cli.
keybase pgp export -s > priv_keybase.txt