open-remote-ssh cannot support remote macOS with download failure for kiro-reh-darwin-arm64.tar.gz

Is there an existing issue for this bug?

• I have searched the existing open issues and found none that apply.
• If I find any issue of interest that is related or closed, I will included a link to it in this issue.

Required Troubleshooting Steps

• I have read and performed the troubleshooting steps
• I have tried both values of the remote.SSH.useLocalServer setting
• My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
• I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar

[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I could NOT successfully SSH to the remote machine, and the error was DIFFERENT than what I saw in VS Code

Remote-SSH Log

[PASTE LOG HERE WITHIN THE BACKTICKS TO FORMAT]

kiro use @https://github.com/jeanp413/open-remote-ssh/ and report error when connect to macos: [Trace - 07:47:22.499] Server install command stderr:
https://prod.download.desktop.kiro.dev/releases/remotes/6124c448360adbeb0adbc771a86db283d2d3f4db/kiro-reh-darwin-arm64.tar.gz:
2025-07-24 15:47:22 ERROR 403: Forbidden.

Expected Behavior

should download the tarball

Actual Behavior

kiro use @https://github.com/jeanp413/open-remote-ssh/ and report error when connect to macos: [Trace - 07:47:22.499] Server install command stderr:
https://prod.download.desktop.kiro.dev/releases/remotes/6124c448360adbeb0adbc771a86db283d2d3f4db/kiro-reh-darwin-arm64.tar.gz:
2025-07-24 15:47:22 ERROR 403: Forbidden.

Steps To Reproduce

connect to macos as remote

Anything else?

No response

Start by reproducing the remote connection to macOS and reviewing the Remote-SSH install command and its output. Investigate why the referenced kiro-reh-darwin-arm64.tar.gz URL returns HTTP 403; the issue is done when the remote server installation can download the required tarball successfully.