# Agent does not wait for powershell commands

**URL:** <https://forum.cursor.com/t/agent-does-not-wait-for-powershell-commands/48866>\
**Category:** Bug Reports\
**Created:** [February 7, 2025, 7:18pm UTC](https://forum.cursor.com/t/agent-does-not-wait-for-powershell-commands/48866 "2025-02-07T19:18:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MaxTeabag](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/maxteabag/32/26732_2.png) [@MaxTeabag](https://forum.cursor.com/u/MaxTeabag)\
**Post date:** [February 7, 2025, 7:18pm UTC](https://forum.cursor.com/t/agent-does-not-wait-for-powershell-commands/48866/1 "2025-02-07T19:18:31Z")

</div>

Often, when the agent runs powershell commands, it interprets that the execution fails even though I didn’t. This leads to writing a modified powershell script while the previous one is running, ignoring the output of it.

 ![FAIL](https://us1.discourse-cdn.com/cursor1/original/3X/1/2/126f47eb6525f1013f5f5caa9a7c612c50ec2aa3.png)

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [February 16, 2025, 1:30pm UTC](https://forum.cursor.com/t/agent-does-not-wait-for-powershell-commands/48866/2 "2025-02-16T13:30:02Z")

</div>

You can probably resolve this by adding a rule for the AI, to tell it ‘Assume terminal commands were successful unless an explicit error is visible in the output!’ and that should stop it from assuming the outcome incorrectly!