I think this might only work with slower/non-local connections. While schema is trying to resolve I think something causes a crash when the tree state changes.
Screenshot attached. I was able to reproduce on local. Once the error occurs, the extension is no longer usable. In the first comment I'll provide the stack trace I got.
Reported on slack.