VS Code plugin and simulator bugs

I've noticed 2 behaviors of the plugin that would be good to have fixed.

1) Often (always?) the first time the simulator is run the simulator window is displayed but the simulation does not start and the DEBUG CONSOLE in VS Code shows

"Unable to connect to simulator". Do another build / run on the simulator and the second time works.

2) when the simulator does run correctly, it consistently "eats" the first keyboard entry, but resonds to subsequent keyboard presses.

Example: Run simulation, click inside the simulator window to move focus there, press ENTER which is taken to be the START / STOP button.

The first time, pressing ENTER does nothing.

The second and all future times, ENTER causes the simulation to behave as if START / STOP was pressed,