galaxy/resources/bundled/skills/feedback/references/logs.md

Log And Crash Artifact Guidance

Use this only for crashes, startup failures, rendering bugs, sync issues, or hard-to-reproduce regressions.

• Ask for logs only when they are likely to improve the report.
• Note in the issue that logs or crash reports were attached, but do not claim they contain console input or output.
• In the Artifacts section, mention the exact file names or bundles that were attached.

macOS paths and commands:

• Logs live under ~/Library/Logs/
• Stable app logs are typically ~/Library/Logs/warp.log*
• Preview app logs are typically ~/Library/Logs/warp_preview.log*
• Stable zip command: zip -j ~/Desktop/warp-logs.zip ~/Library/Logs/warp.log*
• Preview zip command: zip -j ~/Desktop/warp_preview-logs.zip ~/Library/Logs/warp_preview.log*
• If Warp still opens, the user can search View Warp Logs in the Command Palette
• Crash reports may also exist under ~/Library/Logs/DiagnosticReports/ as Warp .ips files

Linux paths:

• Logs live under Warp's state directory.
• Stable app logs are typically ~/.local/state/warp-terminal/warp.log*
• Preview app logs are typically ~/.local/state/warp-terminal-preview/warp_preview.log*
• If the exact channel is unclear, ask the user to open the nearest warp*.log* files under ~/.local/state/

Windows paths:

• Logs live under Warp's local app data state directory.
• Stable app logs are typically %LOCALAPPDATA%\warp\Warp\data\logs\warp.log*
• Preview app logs are typically %LOCALAPPDATA%\warp\WarpPreview\data\logs\warp_preview.log*
• If the exact channel is unclear, ask the user to look under %LOCALAPPDATA%\warp\ for the relevant Warp* folder and attach the matching warp*.log* files from its data\logs\ directory

If no artifacts are available, say so plainly instead of implying they were checked.