For example when a flow in node red turns on a switch it will just say it was done by the supervisor.
It would be more useful for debugging if there was some info related to the specific node red flow responsible for triggering it.
HA has no knowledge of node red. When node red changes something it does so by calling HAs API. When someone calls HAs API the only thing it knows is who the user is, it gets that from the authentication details. In the case of the NR addon it is using supervisor’s access credentials so HA sees it as supervisor. That’s it, it’s not possible for HA to get more context.
That being said there is something you can do if you really want this. You aren’t required to use supervisor’s access credentials nor are you required to use the same config node for all HA nodes in NR. If you go to the config node you can uncheck “I use the addon” and enter a long term access token for a particular user in HA. Then HA will show that the change was triggered by that user. You could then take that further by using different config nodes and different users for HA nodes in different flows since each HA node lets you pick the config node to use at the top. So then when something changed it would say a different user triggered it depending on the flow.
But that’s really the only option. NR is a completely separate project from HA. HA doesn’t have a clue what NR flows are or which are running. If you’re unsatisfied with the debugging options in NR then you should probably submit an FR there.