#Powershell Hard Error on Linting

13 messages · Page 1 of 1 (latest)

untold pollen
#

running bunx oxlint crashes warp with powershell giving hard error (only when an AI agent runs it)

runic vortexBOT
#

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

#

The knowledge sources do not contain enough information to directly address a crash caused by bunx oxlint triggering a PowerShell hard error specifically when run by an AI agent in Warp.

However, there is a related open bug that may be relevant to what you're experiencing:

Possible connection to issue #9899

There is an open Windows bug where Warp crashes with a STATUS_STACK_BUFFER_OVERRUN (0xc0000409) / BEX64 fail-fast when a TUI/AI agent (like Claude Code) streams large output — including output from tool invocations. Key details from that report: [Windows crash bug]

  • The crash is triggered by high-volume TerminalAction::TypedCharacters dispatches during agent-driven terminal output.
  • It only manifests when an AI agent is driving the terminal, not during normal interactive use — which matches your observation.
  • The crash produces no Rust panic, no Crashpad minidump, and no Sentry report; Windows WER captures it instead.
  • A later update made the crash reachable even from small amounts of output (as few as 7 TypedCharacters dispatches).

A linter like oxlint can produce a large burst of structured output (warnings, errors, file paths), which could trigger the same path.

Suggested workarounds (from the issue)

  • Have the agent redirect linter output to a file instead of streaming it to the terminal:
    bunx oxlint > lint-output.txt 2>&1
  • Then read the file separately.

Recommended next steps

  1. Check Windows Event Viewer (Application log) around the crash time for a warp.exe entry with Exception code: 0xc0000409 — this would confirm it's the same bug family.
  2. Add a comment or upvote on issue #9899 with your reproduction details, as it's actively being triaged.
#

The issue is currently open and unresolved as of the latest information available.

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

#

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

untold pollen
#

workaround?

shy vortex
#

@runic vortex workaround?

untold pollen
#

Its impossible to use agents in warp now, i had to switch back to windows terminal

shy vortex
#

please open a new github bug report, use the /feedback skill in Warp or go to the github page. @runic vortex please provide info for these two options.

runic vortexBOT
#

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

#

Here are the two ways to file a bug report for this issue:

Option 1: Use /feedback inside Warp

Type the following slash command directly in your Warp terminal:

/feedback
  • If AI is enabled: The Agent will draft and file the GitHub issue for you. It will classify the report, ask clarifying questions if needed, check for duplicates, and file against warpdotdev/warp. Note this consumes credits.
  • If AI is disabled: Warp opens the GitHub new-issue picker in your browser with your Warp version and OS prefilled.

[/feedback command]

Option 2: File directly on GitHub

Go to: [https://github.com/warpdotdev/warp/issues/new/choose](https://github.com/warpdotdev/warp/issues/new/choose)

What to include in your report

A good bug report should answer: [what to include]

#
  • What happened: Warp crashes with a PowerShell hard error when an AI agent runs bunx oxlint.
  • What was expected: The linter runs and returns output without crashing Warp.
  • Steps to reproduce: Have an AI agent execute bunx oxlint in a PowerShell session inside Warp on Windows.
  • Warp version: Copy from Settings > Account.
  • Logs: Zip and attach your Windows logs with:
    Compress-Archive -Path "$env:LOCALAPPDATA\warp\Warp\data\logs\warp.log*" -DestinationPath "$([Environment]::GetFolderPath('Desktop'))\warp-logs.zip"
  • Windows Event Viewer: Check the Application log around the crash time for a warp.exe entry — look for Exception code: 0xc0000409, which would link this to the known issue #9899.
  • Reference: Mention issue #9899 as a likely related bug.

[gathering logs]

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