The keycommands behaviour within the tree view is very erratic. For example when renaming a layer or element, typing w or d changes the selection of the element and jumps out of the text field. There’s many other bugs like this. It’s really inconsistent and feels very buggy. I’m on reaper 7.56 on win10. halion 7.1.20.775 (64bit)
Seems like the tree view (also the program list, similar key command behaviour!) is still buggy based on the newest update. Is halion passing the keycommands forward to the daw even tho those are used by the app? it seems to me like it does… makes it very erratic.
It’s the other way round. The DAW or Host will pass through the keystrokes to the plugin. If this doesn’t work correctly it’s of course erratic.
In Bitwig, Fender Studio, Cubase/Nuendo and Standalone it works as desired, so most likely Reaper needs an update.
best regards
Gerrit
Ok I will pass this on to the developers on that end 
thank you, just based on the conversation around this in the past it seemed to me it might be plugin issue.
Heres some of the erratic behaviour. it seems like the spacebar and such are only passing to the daw when theres no text fields. So that might actually be correct behaviour. Just in case this is somehting within your domain of influence. Dropbox
the key commands are registered properly when I tick a setting within reaper to just push all key commands to the plugin, but now im getting this kind of behaviour 
so the key commands arent targetting the text field properly. but are sent off to the plugin gui.
btw, so the text field bug exsist even tho the “send all keycommands to plugin” setting is disabled. so thats no the cause of it.
so basically when i have hit rename on the program table or on a node in the tree view. pressing the “A” “W” “backspace” or “D”keys for example will run those keycommands in the tree view, and the keys dont go into the open text field. so you end up deleting nodes and navigating the treeview randomly when you wanted to rename the program.