How to handle new keys for users already following

I am following the user grabe. In just trying out the command line version today I did:

➜  ~ keybase id grabe
▶ INFO Identifying grabe
✔ <tracked> public key fingerprint: A7CE 0DFF 6DB8 548A 87F7 D75A 8223 B114 C34C 8CA2
✔ <new> public key fingerprint: A647 3C85 C010 2F36 BE06 D012 3F80 12D0 340D 7077
✔ <new> public key fingerprint: 0D99 7A58 D966 ACB0 F504 A731 1013 FC11 E667 1968
You last followed grabe on 2017-05-11 18:08:27 PDT
✔ <tracked> "sowce" on facebook failed: No server-given hint for sig=b8655262a3e84d3d1f847447c0e6525b1bc590ba2a3b49d13a8fa0a8740ff87a0f (code=306)
✔ <tracked> "gabeschamberg" on github: https://gist.github.com/4c2065b56aa6f483f8da26c4270979d6 [cached 2017-05-16 10:18:10 PDT]

But when I try to pull those new keys, I get:

➜  ~ keybase pgp pull grabe
▶ INFO Imported key for grabe.
▶ WARNING Keybase says that grabe owns key a6473c85c0102f36be06d0123f8012d0340d7077, but you have not tracked this fingerprint before.
▶ WARNING Keybase says that grabe owns key 0d997a58d966acb0f504a7311013fc11e6671968, but you have not tracked this fingerprint before.

Am I missing something about how "following" works? How should I handle this?

Reproduce the reported behavior with the keybase id grabe and keybase pgp pull grabe entry points, comparing the tracked and new fingerprints shown in the output. Trace how following and PGP key import are connected, then document the expected handling for keys that were not previously tracked.