Sending feedback and logs

Sending Warp feedback

• Use the /feedback slash command inside Warp to open the static feedback experience.
• Open a new bug or feature request in our GitHub repository.
• Join our Warp Community Slack and share feedback in #feedback-general, or #feedback-preview if it is specific to Warp Preview.
• For security issues or questions, email security@warp.dev.
• For questions about privacy, email privacy@warp.dev.

Subscribers and Enterprise

• For subscriber technical issues or questions (bugs, credits, etc.), email support@warp.dev.
• For subscriber billing issues or questions (refunds, cancellation, etc.), email billing@warp.dev.
• For enterprise, please direct all feedback and issues to your designated Slack channel.

Using /feedback in Warp

The /feedback slash command is the fastest way to report a Warp bug, flag a regression, or file a feature request from inside the terminal. It opens the feedback form without starting an Agent conversation or consuming credits.

What to include

Whether you use the /feedback slash command or file an issue manually, a good feedback report answers these questions up front:

• What happened? Describe the observed behavior in one or two sentences.
• What did you expect? Describe the behavior you expected instead.
• How do we reproduce it? List numbered steps when possible. If you can’t reproduce the issue reliably, mention that too.
• What version of Warp are you on? /feedback fills this in automatically; for manual reports, copy it from Settings > Account.
• Logs, screenshots, or conversation IDs. See Gathering Warp logs, Collecting crash reports on macOS, or Gathering AI conversation ID below.

See the Slash Commands reference for the full list of commands available in Warp.

Gathering Warp logs

Retrieve Warp’s logs by following the instructions for your platform below. Locate the log file and attach it to your GitHub issue or email.

Note

Warp’s logs and crash reports do not contain any console input or output. See more on how we handle Crash Reports and Telemetry.

macOS

The Warp log files are located at ~/Library/Logs/.

Warp logs on macOS

Run the following to zip the Warp logs to your Desktop:

zip -j ~/Desktop/warp-logs.zip ~/Library/Logs/warp.log*

Warp Preview logs on macOS

Run the following to zip the Warp Preview logs to your Desktop:

zip -j ~/Desktop/warp_preview-logs.zip ~/Library/Logs/warp_preview.log*

Caution

If your issue is graphical (e.g. no display of windows) or a crash, run Warp with the following command to capture more log information:

# Run if Warp on macOS is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/Warp.app/Contents/MacOS/stable

# Run if Warp Preview on macOS is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/WarpPreview.app/Contents/MacOS/preview

Windows

The Warp log files are located at $env:LOCALAPPDATA\warp\Warp\data\logs\.

Warp logs on Windows

Close Warp and run the following from another terminal to zip the logs to your Desktop:

Compress-Archive -Path "$env:LOCALAPPDATA\warp\Warp\data\logs\warp.log*" -DestinationPath "$([Environment]::GetFolderPath('Desktop'))\warp-logs.zip"

Warp Preview logs on Windows

Close Warp Preview and run the following from another terminal to zip the logs to your Desktop:

Compress-Archive -Path "$env:LOCALAPPDATA\warp\WarpPreview\data\logs\warp_preview.log*" -DestinationPath "$([Environment]::GetFolderPath('Desktop'))\warp_preview-logs.zip"

Caution

If your issue is graphical (e.g. no display of windows) or a crash, run Warp with the following command to capture more log information:

# Run if Warp on Windows is installed for a single user
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:LOCALAPPDATA\Programs\Warp\warp.exe"

# Run if Warp on Windows is installed for all users
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:PROGRAMFILES\Warp\warp.exe"

# Run if Warp Preview on Windows is installed for a single user
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:LOCALAPPDATA\Programs\WarpPreview\preview.exe"

# Run if Warp Preview on Windows is installed for all users
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:PROGRAMFILES\WarpPreview\preview.exe"

Linux

The Warp log files are located at ~/.local/state/warp-terminal/.

Warp logs on Linux

Run the following to zip the Warp logs to your home directory:

(cd ~/.local/state/warp-terminal && tar -czf ~/warp-logs.tar.gz warp.log*)

Warp Preview logs on Linux

Run the following to zip the Warp Preview logs to your home directory:

(cd ~/.local/state/warp-terminal-preview && tar -czf ~/warp_preview-logs.tar.gz warp_preview.log*)

Caution

If your issue is graphical (e.g. no display of windows) or a crash, run Warp with the following command to capture more log information:

# Run if Warp on Linux is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal

# Run if Warp Preview on Linux is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal-preview

Collecting crash reports on macOS

If Warp crashes, macOS may generate .ips crash report files in ~/Library/Logs/DiagnosticReports/. Run the following to collect all Warp crash reports into a zip on your Desktop:

files=$(find ~/Library/Logs/DiagnosticReports -name "*.ips" -exec grep -l "dev\.warp" {} + 2>/dev/null) && [ -n "$files" ] && echo "$files" | xargs zip -j ~/Desktop/warp-crash-logs.zip || echo "No Warp crash reports found."

Attach the resulting warp-crash-logs.zip to your bug report.

Note

This command searches crash report files for Warp’s bundle identifier, so it works across all Warp channels (Stable, Preview).

Collecting debug info on Windows

Occasionally, the Warp team may ask you to provide debugging information on Windows OS in particular with one of the following:

# If Warp is in your PATH, Run:
warp --dump-debug-info

# Otherwise you may need to use an absolute path and ...
# Warp on Windows is installed for a single user, Run:
& $env:LOCALAPPDATA\programs\Warp\warp.exe --dump-debug-info

# Warp on Windows is installed for all users, Run:
& $env:PROGRAMFILES\Warp\warp.exe --dump-debug-info

Collecting CPU samples

Certain conditions can cause Warp to use more CPU than expected or become unresponsive. Collecting a CPU sample while the issue is happening is the best way to report it. The sample provides the information the Warp team needs to identify and fix the root cause.

Collect a sample using the steps for your platform and attach it to a new GitHub issue.

macOS

1. Reproduce the high CPU usage or unresponsiveness in Warp.
2. While the issue is occurring, open Activity Monitor, select the Warp process, and click Sample Process.

Sampling a Warp process in Activity Monitor.

3. Save the resulting sample and attach it to your GitHub issue.

Windows

Install samply to record a CPU trace:

powershell -ExecutionPolicy Bypass -c "irm https://github.com/mstange/samply/releases/download/samply-v0.13.1/samply-installer.ps1 | iex"

1. Find the Warp process ID:

   Get-Process *warp*

2. Start recording, replacing <PID> with the process ID from the previous step:

   samply record -p <PID>

3. Reproduce the issue that causes high CPU usage or unresponsiveness.

4. Press Ctrl+C to stop recording. samply opens the profile in the Firefox Profiler in your browser. Click the upload icon in the top-right corner to generate a shareable link, then paste it into your GitHub issue.

Linux

Install samply to record a CPU trace:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mstange/samply/releases/download/samply-v0.13.1/samply-installer.sh | sh

Caution

samply requires access to Linux perf events. If you get a permission error, run:

echo '-1' | sudo tee /proc/sys/kernel/perf_event_paranoid

1. Start recording the Warp process:

   samply record -p $(pgrep -f warp-terminal)

2. Reproduce the issue that causes high CPU usage or unresponsiveness.

3. Press Ctrl+C to stop recording. samply opens the profile in the Firefox Profiler in your browser. Click the upload icon in the top-right corner to generate a shareable link, then paste it into your GitHub issue.

Note

If you prefer not to install samply, you can use the built-in perf tool instead:

perf record -g -p $(pgrep -f warp-terminal) -- sleep 30

Attach the resulting perf.data file from your current directory to your GitHub issue.

Gathering AI conversation ID

To gather the conversation ID, RIGHT-CLICK on the AI conversation block in question and select “Copy conversation ID”, then paste that into the bug report that you submit so that our team can investigate the issue.

Whenever there is an error in the Agent Conversation, there will also be an option to directly copy the conversation ID for the bug report.

Using /copy-debugging-id

The /copy-debugging-id slash command copies the same information without leaving the input. It works in both the Warp app and the Warp Agent CLI, and it applies to the conversation you’re currently in:

1. Run /copy-debugging-id in the conversation you want to report.
2. Warp confirms with a “Debugging information copied to clipboard” message.
3. Paste the copied text into your bug report.

The copied text is a small JSON payload with the conversation ID, plus the request ID when the command is run on a specific agent response — for example, {"conversation_id":"abc123"}. If the conversation hasn’t reached Warp’s servers yet, the command reports that no debugging ID is available; send a prompt first, then run it again.