Usability: Warp Agent Crashes with PSReadLine Error

[austere bison]

Usability: Warp Agent Crashes with PSReadLine Error

Environment:

• OS: Windows 10 (win32 10.0.26100)
• Warp Version: Latest (as of 2025-07-09)
• Shell: PowerShell (C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe)
• Workspace Path: <WORKSPACE_PATH>

Description:
The Warp agent crashes with a System.ArgumentOutOfRangeException in PSReadLine when creating example.md via PowerShell for an amoCRM widget project. It processes logs (console logs/) and SDK files (<INSTRUCTIOINS_PATH>/<SDK_PATH>/), but fails on:

. { . { @"..."@ } | Out-File -FilePath "<WORKSPACE_PATH>\example.md" -Encoding UTF8 -Force }

Error:

• Exception: System.ArgumentOutOfRangeException: The value must be greater than or equal to zero and less than the buffer size in this dimension. Parameter name: top. Actual value was -96/-160.
• Source: System.Console.SetCursorPosition in Microsoft.PowerShell.PSConsoleReadLine.
• Additional Error: Exception calling "BackwardDeleteLine" with "0" arguments: "The value must be greater than or equal to zero and less than the buffer size in this dimension. Parameter name: top. Actual value was -160."

Steps to Reproduce:

1. Set up a project in Warp at <WORKSPACE_PATH>.
2. Instruct agent to create an .md file using PowerShell (Out-File, UTF-8).
3. Agent reads logs and SDK files.
4. Agent executes nested PowerShell command.
5. Warp crashes with the error.

Expected:

• Agent creates .md file without crashing.
• No PSReadLine errors.

Actual:

• Agent outputs logs, then crashes during PowerShell execution.

Tried:

• Restarted Warp.
• Verified UTF-8 encoding.
• Simplified instructions, but the crash persists. (Side note: trying to work around this burned over 1,500 requests in a few days, ouch!)

Details:

• Project: amoCRM widget with 104 .md SDK files, logs, script.js.
• Tools: grep_search, read_file, PowerShell per user_rules.md.

[toxic ferry]

Hi @austere bison. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

I'm sorry, but the knowledge sources do not contain any explicit information about a Warp agent crashing with a PSReadLine System.ArgumentOutOfRangeException when creating files via PowerShell, or about handling this specific error scenario in the context you described.

However, there are several related issues in the knowledge sources involving PSReadLine errors and PowerShell integration problems in Warp on Windows. For example, some users have encountered errors when Warp attempts to use PowerShell 5.1, which may lack certain modules or compatibility with PSReadLine features, leading to startup failures or shell crashes. In those cases, switching to PowerShell 7.x and ensuring PSReadLine is properly installed has sometimes resolved the issue. There are also reports of errors related to cursor position and console buffer handling in PowerShell, but none that exactly match the System.ArgumentOutOfRangeException you described.

If you are running into persistent PSReadLine errors, you might try the following based on related issues:

• Ensure you are using PowerShell 7.x, not 5.1, as Warp prefers 7.x and it has better compatibility with modern modules and features.
• Make sure PSReadLine is installed and up to date in your PowerShell environment.
• If you have custom profile scripts, try commenting them out to see if the issue persists, as certain configurations can cause shell startup failures in Warp.
• If you are using a non-standard installation path for PowerShell, try reinstalling it to the default path, as Warp may have trouble detecting custom locations.
• If the error only occurs in Warp and not in other terminals, consider sending your logs to the Warp team for further debugging, as suggested in several issues.

Unfortunately, without more specific information in the knowledge sources, I cannot provide a definitive solution for your exact error. If you haven't already, you may want to open a new issue on the Warp GitHub with detailed logs and reproduction steps, as this will help the developers investigate and address the problem more directly.

If you have additional details or logs, I can help you interpret them or look for related patterns in the knowledge sources.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@austere bison Kapa.ai is still learning and improving, please let me know how I did by reacting below.

[austere bison]

Updated to PowerShell 7.5.2 in Warp 2. Now terminal auto-inserts 'i', causing error: "i.: The term 'i.' is not recognized..." when running commands like Set-Content -Path "example\path\example.md". Example: i^P. { . { @"...>>"@ | Out-File ... } }. No issue in standalone PowerShell 7. Any fix for input handling?

@toxic ferry

[toxic ferry]

Let me check the knowledge base for you again. One moment! :books:

Sorry @austere bison, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

[austere bison]

@toxic ferry

[toxic ferry]

Let me check the knowledge base for you again. One moment! :books:

Sorry @austere bison, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

[austere bison]

@toxic ferry 🚨 CRITICAL BUG: Warp AI Agent PowerShell Integration Completely Broken

SIMPLE REPRODUCTION:

1. Open Warp with PowerShell 7.5.2
2. Ask AI Agent to run ANY command: echo "test"
3. Command fails: "kecho: term not recognized"

ISSUE: Extra character "k" (or "i" or "з" in other sessions) prepended to EVERY command

IMPACT:

• 100% failure rate for all PowerShell commands in AI Agent
• Renders AI Agent unusable for Windows users
• Cost me 1500+ requests trying to work around this

This is a transmission bug between AI Agent → PowerShell, not user config.

Evidence: Same commands work fine in standalone PowerShell 7.5.2

[toxic ferry]

Let me check the knowledge base for you again. One moment! :books:

---

Thank you for your detailed report. Based on the knowledge sources, the issue you’re describing—where an extra character (such as "i", "k", or "з") is prepended to every command executed by the AI Agent in Warp’s PowerShell integration—is a known and critical bug affecting Windows users.

Key findings from the knowledge sources:

• Multiple users have reported that Warp on Windows sometimes prepends extra characters (like "i", "i^P", or other letters) to every command, causing all commands to fail (e.g., kecho: term not recognized) [Windows 11: The letter "i" is echoed after every command, Warp Terminal automatically adds "i^" prefix to every entered command, i^P prefix].
• This bug is not related to user configuration or PowerShell profile scripts. It is a transmission or input handling bug between Warp (and specifically the AI Agent) and the PowerShell process.
• The issue is often triggered or made worse by having a non-English keyboard layout active when launching Warp. For example, if you start Warp with a Turkish or Russian keyboard layout, the extra character appears, even if you switch back to English afterward [Warp Terminal automatically adds "i^" prefix to every entered command].
• Restarting Warp with the keyboard set to English (US or UK) sometimes temporarily resolves the issue, but it can recur, especially after updates or when using Agent Mode.
• The bug is confirmed to be a regression and has been acknowledged by the Warp team, who are working on a fix. Users are encouraged to provide logs to help with debugging [Warp Terminal automatically adds "i^" prefix to every entered command].

Workarounds (from user reports):

• Before launching Warp, set your keyboard layout to English (US or UK). Then start Warp. This may prevent the extra character from appearing.
• If the issue occurs after an update, try fully quitting and restarting Warp.
• For some users, explicitly selecting PowerShell as the shell for new tabs (instead of using the default "+") has temporarily resolved the issue [i^P prefix].

Summary:
This is a known, critical bug in Warp’s Windows PowerShell integration, especially affecting the AI Agent. It is not caused by user configuration and is under active investigation by the Warp team. The only current workaround is to ensure your keyboard layout is set to English before launching Warp, but this is not a guaranteed fix. The issue is not present in standalone PowerShell.

If you haven’t already, please provide your logs to the Warp team to assist with their investigation. They are aware of the severity and are working on a permanent fix.

For more details and updates, see these related issues:

• Windows 11: The letter "i" is echoed after every command
• Warp Terminal automatically adds "i^" prefix to every entered command
• i^P prefix

---

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@austere bison Kapa.ai is still learning and improving, please let me know how I did by reacting below.

[austere bison]

@toxic ferry Important clarification: I'm on Windows 10 (not Windows 11 as mentioned in the sources).

Environment details:

• OS: Windows 10 build 26100
• PowerShell: 7.5.2 (pwsh)
• Issue: Same extra character prepending problem

Please ensure the fix covers Windows 10 users, not just Windows 11. The bug affects both OS versions.

[toxic ferry]

Let me check the knowledge base for you again. One moment! :books:

---

Thank you for clarifying that you are on Windows 10 (build 26100) with PowerShell 7.5.2. Based on the knowledge sources, the bug where an extra character (such as "i", "k", or "з") is prepended to every command in Warp’s PowerShell integration is not limited to Windows 11—it also affects Windows 10 users.

The reports and discussions in the sources reference both Windows 10 and Windows 11 environments experiencing this issue. For example, users on Windows 10 have reported the same problem with extra characters being prepended to commands, leading to failures in command execution. The bug is related to how Warp handles input transmission to PowerShell, and is not specific to a particular Windows version or user configuration [Windows 11: The letter "i" is echoed after every command, Warp Terminal automatically adds "i^" prefix to every entered command, i^P prefix].

Summary:
The fix for this bug must cover both Windows 10 and Windows 11, as the issue is present on both OS versions. The Warp team is aware of the problem and is working on a solution that should address it across all supported Windows platforms.

If you haven’t already, you may want to provide your logs to the Warp team to help ensure the fix is thoroughly tested on Windows 10 as well.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@austere bison Kapa.ai is still learning and improving, please let me know how I did by reacting below.

[austere bison]

@toxic ferry Important clarification: I'm on Windows 10 (not Windows 11 as mentioned in the sources).

Environment details:

• OS: Windows 10 Pro 22H2 (Build 19045.5737)
• PowerShell: 7.5.2 (pwsh)
• Issue: Same extra character prepending problem

Please ensure the fix covers Windows 10 users, not just Windows 11. The bug affects both OS versions.

[toxic ferry]

Let me check the knowledge base for you again. One moment! :books:

---

Thank you for your clarification regarding Windows 10 Pro 22H2 (Build 19045.5737) and PowerShell 7.5.2. Based on the knowledge sources, the issue where an extra character (such as "i", "k", or "з") is prepended to every command in Warp’s PowerShell integration is not limited to Windows 11. There are multiple user reports and discussions confirming that this bug also affects Windows 10 environments.

For example, users have reported the same input-prepending problem on Windows 10, and the Warp team has acknowledged that the bug is not OS-version specific. The root cause appears to be related to how Warp handles keyboard input and shell integration, especially when non-English keyboard layouts are involved or after certain updates. The issue is not tied to user configuration or PowerShell profile scripts, and restarting Warp or ensuring the keyboard layout is set to English before launch are only temporary workarounds [Warp Terminal automatically adds "i^" prefix to every entered command, i^P prefix].

In summary:
The fix for this bug must address both Windows 10 and Windows 11, as the problem is present on both OS versions. The Warp team is aware of the cross-version impact and is working on a solution. If you are affected, providing logs and details to the Warp team will help ensure the fix is validated for Windows 10 as well.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: