Regression: .command files open in editor instead of executing

[ScruffyDogg325]

Description

Warp no longer executes .command files when opened. Instead, it opens them in Warp's built-in editor for editing. This is a regression — Warp was correctly executing .command files for years prior to a recent update (noticed around early April 2026).

Steps to Reproduce

1. Create or use an existing .command file with executable permissions (chmod +x) and a valid shebang (e.g. #!/bin/zsh).
2. Set Warp as the default application for .command files.
3. Double-click the .command file in Finder, or have it configured as a Login Item.

Expected: Warp opens a new terminal session and executes the script.
Actual: Warp opens the file in its built-in text editor for editing.

Environment

• macOS (Apple Silicon)
• Warp latest stable (as of April 2026)
• File has -rwx------ permissions and a #!/bin/zsh shebang

Impact

This breaks workflows that rely on .command files as Login Items to start services (e.g. game servers) at system startup, since the user needs an interactive terminal session to interact with the running process.

Workaround

Reassigning .command files to Terminal.app restores execution behavior, but loses the benefits of using Warp as the terminal.

Notes

• Clearing extended attributes (xattr -c) did not resolve the issue.
• The Warp documentation confirms that .command file execution is a supported feature.