Summary

The /feedback slash command filed an issue (#9542) in which the Warp version field was recorded as Unknown rather than the actual installed version. The reporter confirmed they were running v0.2026.04.27.15.32.stable_03 at the time.

Problem

The feedback skill is expected to read the bundled version metadata file (metadata/version.json relative to the skill package) and populate the Warp version field automatically. In this case the field was left as Unknown, meaning the skill either could not locate or could not read the version metadata at filing time.

@captainsafia flagged this in the comment thread and suspects it may be related to how version metadata is bundled for different binary or platform variants.

Expected behavior

The /feedback skill should reliably detect and include the installed Warp version (e.g. v0.2026.04.27.15.32.stable_03) in the Warp version field of every filed issue.

Actual behavior

The Warp version field in the filed issue (#9542) was Unknown. The reporter confirmed they were running v0.2026.04.27.15.32.stable_03 at the time.

Reproduction steps or desired workflow

1. Use the /feedback slash command in Warp to file an issue on macOS Sequoia.
2. Check the resulting GitHub issue's Warp version field.
3. Observe that the field reads Unknown rather than the actual installed version.

Artifacts

None attached.

Related comment: #9542 (comment)

Debugging ID from the originating /feedback run: [reporter to fill in]

Warp version

v0.2026.04.27.15.32.stable_03 (at time of original /feedback run)

Operating system

macOS 15.6.1 (Sequoia, build 24G90)

Possible source references

• Bundled skill metadata file ../../metadata/version.json (relative to skill root): the file the skill reads to populate Warp version; appears to have been missing, unreadable, or not found at filing time
• scripts/resolve_platform.py: bundled helper for OS resolution; version resolution is handled separately via the metadata file and may not share the same failure mode