Suggest to add a loading state between the Run and Stop button

I'm testing long prompts around 3.2k tokens using GPT-4 and have wasted quite a few credits.Sometimes the Run button is not very responsive (especially when the prompt is saving or the token size is a bit large). There may be a half to one-second delay before it actually starts running. I accidentally double-click because I think I didn't press the Run button the first time. As a result, the second click actually hits the Stop button.There needs to be a longer delay when changing the Run button to the Stop button. Maybe add a loading state.