Pasted PowerShell code re-aligns once invoked.

[RokeJulianLockhart]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

When I paste PowerShell (Core) code into Warp, it separates the code into multiple segments, and misaligns the pasted code:

This does not reproduce in Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe:

To reproduce

Duplicate the undermentioned:

#!/usr/bin/env pwsh
Get-ComputerInfo | Select-Object -Property @(
	'OsName',
	'OsOperatingSystemSKU',
	'OsVersion',
	'OsBuildNumber'
) | Format-List

...into the clipboard:

When duplicated into the clipboard, duplicate the content from the clipboard into Warp:

When executed, the shebang shall be separated, and the input shall appear misaligned:

For comparison, see the behaviour when pasted into Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe:

1. 

2. 

3. 

Expected behavior

It should not separate the shebang from the rest of the code, and should not modify the code alignment once pasted.

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

cpe:/o:microsoft:windows_11_24h2

Shell Version

Microsoft.PowerShellPreview_7.6.4.0_x64__8wekyb3d8bbwe

Current Warp version

v0.2025.05.21.08.11.stable_01

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

I do not know.

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[dannyneira]

Hi @RokeJulianLockhart, thanks for letting us know. I was able to reproduce this issue, but noticed that if you exclude the shebang line, the command runs and formats correctly. Since the shebang is not required unless it's the top line of a .ps1 script, you can exclude it from the input as a workaround (or add it to and run a .ps1 script file). That being said, I'll submit this to the team as room for improvement.

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.